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
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.docs/context/GOALS.md: objectives, milestones, priorities.BACKLOG.md: the Inbox for unprocessed items, Triaged for P0/P1 items.- 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):
- [highest-priority action, based on goals, status and blockers]
- [second priority]
- [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.