Agent Blueprint
Get started
Session management

ab-project-status

Where the project stands: code state, work in flight, goal progress, top three next actions

/ab-project-status
Read SKILL.md on GitHub
Skill
ab-project-status
Phase
Session management, 6 of 9
Version
4.2.0
Starts
When named, or on a matching request
Helpers
None
File
skills/ab-project-status/SKILL.md

Use it when

  • When the user asks for status, an overview or summary, what is going on, what is next or what the priorities are, or wants to get oriented at the start of a session

Pick another skill

Not for resuming a prior session's tasks (ab-resume-session), a build, test and lint health check (ab-health-check), or setting up a new project (ab-project-start).

ab-resume-sessionReloads what earlier sessions left and checks whether HEAD moved since the handoffab-health-checkEight areas (build, tests, lint, dependencies, conventions, docs, backlog, git) checked with the project's own commandsab-project-startScaffolds AGENTS.md, CLAUDE.md, docs/context/ and BACKLOG.md by merging, then fills in conventions, goals and status

Name it in your tool

Every tool also picks a skill on its own when your request matches its description. Naming it picks it for sure.

Claude Code

in a session
/ab-project-status

What it does

Reports where the project stands: reads docs/context/STATUS.md (its Session Continuity section first), GOALS.md, BACKLOG.md and the git state, then presents the code state, work in flight, goal progress, what needs attention and the top three next actions with reasons.

The sections of its SKILL.md

  1. Read

  2. Report

What you get back

As its SKILL.md defines it, under Report.

Project Status — [date]

Code State:

  • Build, test and lint status from STATUS.md
  • Current branch and uncommitted changes from git

In Flight:

  • [table of active work from STATUS.md, with blockers highlighted]

Goal Progress:

  • [which objectives and milestones are advancing, which are stalled]

Attention Needed:

  • [P0/P1 backlog items not yet in flight]
  • [blocked items and what unblocks them]
  • [known issues by severity]
  • [count of unprocessed Inbox items]

Suggested Next Actions (top 3):

  1. [highest-priority action, based on goals, status and blockers]
  2. [second priority]
  3. [third priority]

Give the reasoning for each suggestion: why this one over the other options, so the user can disagree with the reason rather than just the pick.

SKILL.md

The instructions the agent follows, from skills/ab-project-status/SKILL.md.

Read SKILL.md on GitHub

Project Status

The outcome is a short status report the user can act on, ending in three suggested next actions with the reason for each. It reads and reports only; it changes no files.

Read

  1. docs/context/STATUS.md: its Session Continuity section (where the last session left off), then work in flight, what is done, known issues and blockers.
  2. docs/context/GOALS.md: objectives, milestones, priorities.
  3. BACKLOG.md: the Inbox for unprocessed items, Triaged for P0/P1 items.
  4. The git state: 
    git log --oneline -10
git status
git branch --show-current

If docs/context/ does not exist, say so and suggest the ab-project-start skill instead of guessing a status.

Report

Project Status — [date]

Code State:

  • Build, test and lint status from STATUS.md
  • Current branch and uncommitted changes from git

In Flight:

  • [table of active work from STATUS.md, with blockers highlighted]

Goal Progress:

  • [which objectives and milestones are advancing, which are stalled]

Attention Needed:

  • [P0/P1 backlog items not yet in flight]
  • [blocked items and what unblocks them]
  • [known issues by severity]
  • [count of unprocessed Inbox items]

Suggested Next Actions (top 3):

  1. [highest-priority action, based on goals, status and blockers]
  2. [second priority]
  3. [third priority]

Give the reasoning for each suggestion: why this one over the other options, so the user can disagree with the reason rather than just the pick.