next-steps
Status overview of an .aiwork/ task folder — what is done, what is awaiting the human, what is blocked, and the one next action. Auto-detects the most recent task folder when no argument is given.
SKILL.mdplugins/aiwork/skills/next-steps/SKILL.md
GitHubNext Steps
Read-only status report for one .aiwork/ task folder. Follows the aiwork-protocol skill; changes nothing.
1. Resolve input
$ARGUMENTS is a spec, plan, ticket, or task folder path. A file path resolves to its task folder (a ticket's is the folder above tickets/). With no args, find the most recently modified task folder per aiwork-protocol conventions. Nothing found → say so and stop.
2. Gather
Read frontmatter first, prose only where needed.
intent.md:status(proposed/accepted/declined).spec.md(or the currentplan*.mdwhen there is no spec, skipping any withsuperseded_by):status,blocked_by,verified. Note whether the spec still has open questions, TBDs, or a non-empty Open Concerns section.tickets/, if present: for each ticket its number, title,status(ready/in-progress/done),blocked_by,verified, and the count of ticked vs unticked acceptance criteria. The frontier is everyreadyticket whose blockers are alldone.review*.md: present or not, and itsreviewed_sha.implementation-notes*.md: any entries the human must act on.
Read the vocabulary as the protocol defines it:
- Ticket folders carry the truth in ticket statuses; the spec's own
statusis optional there. - Without tickets, an absent spec
statusmeans unknown, not not-started. agent-donemeans the agent finished and handed over; report it as awaiting the human's check, never as finished.doneon a spec is the human's call.- Older folders may use
draft/active/complete/superseded; map them to the nearest current value and say so.
3. Report
Brief. Print, in order:
- Headline: task folder, then one line — intent status, spec status (or "tickets: N done / M in progress / K ready / J blocked").
- Tickets table when
tickets/exists: number, title, status, blockers, criteria ticked,verifiedpasses. Skip the table for folders without tickets. - Next action, exactly one line, first match wins:
- intent not
accepted→ decide the intent (/aiwork:to-specwaits on it) - no spec and no tickets →
/aiwork:to-spec - spec with open questions / Open Concerns → resolve them;
/aiwork:implement-specstops on them - spec, no tickets, not small →
/aiwork:to-tickets; small →/aiwork:implement <spec> - frontier non-empty →
/aiwork:implement-spec, or/aiwork:implement tickets/<NN>naming the first frontier ticket - a ticket
in-progress→ resume it - all tickets
done, noreview*.md→/aiwork:implement-specruns the wrap-up review - spec
agent-done→ the human exercises the feature and reads the code, then setsdone - spec
done→ all done - spec
blockedor every remaining ticket blocked → name the blocker
- intent not
- Needs a human: only if any exist —
blocked_bycauses, unresolved implementation notes,donetickets with unticked criteria or without an on-appverifiedpass (behaviour/ux/human), a review whosereviewed_shais missing.