Run the full acceptance testing pre-flight pipeline for a feature. Use when asked to "run acceptance prep", "run the pre-flight pipeline", "prepare for acceptance testing", "run [ACCEPTANCE-PREP]", or when an [ACCEPTANCE-PREP] issue is open and ready to start. Orchestrates all four pipeline layers: demo agent, adversarial reviewer, real-data stress agent, synthesis agent. Produces the synthesis brief that the human uses to run the [ACCEPTANCE] session.
Walk through a single feature or flow using the demo agent persona. Use when asked to "demo this feature", "walk me through [flow]", "show me what was built", "run acceptance walkthrough for [feature]", or when validating one specific flow without running the full pre-flight pipeline. Produces a focused ACCEPTANCE-DEMO.md for a single flow. Does not run the adversarial reviewer or real-data stress agent — use acceptance-prep for the full pipeline.
Read the project spec and produce a phased implementation plan: modules identified, ordered by dependency, grouped into phases. Use when asked to "break down the spec", "create an implementation plan", "phase the work", "what order do we build things", or "plan the tickets". Output is a phase plan the engineer reviews and approves before draft-tickets runs on each phase. Does not create tickets — that's draft-tickets.
Draft an agent briefing document (CLAUDE.md or equivalent) from the project spec and existing toolchain configuration. Use when asked to "draft CLAUDE.md", "create the agent briefing doc", "write CLAUDE.md from the spec", or "set up CLAUDE.md". Produces a first draft covering all 7 sections of the briefing framework, with [NEEDS INPUT] markers where the spec doesn't provide enough detail. Run review-claudemd on the output before committing.
Draft the [TEST] and [IMPL] ticket content for one phase of the implementation plan. Use when asked to "draft tickets for phase N", "write tickets for [module]", "create the TEST and IMPL issues for [phase]", or "prepare the next phase tickets". Produces filled-in ticket content for every module in the phase, ready for review-issue to validate before the tickets are opened. Run one phase at a time.
Run the decision narration workflow to capture a design or architectural decision made during an AI coding session. Use when asked to "capture this decision", "generate a decision record", "narrate this decision", "let's do a session mini-retro", or "before I close this window." Goal: move reasoning from the engineer's head into a Decision Record while session context is still live. The record goes into the PR alongside the code change.
Run a post-IMPL retro to identify what should be encoded into setup artifacts before the next ticket. Use when asked to "run the retro", "do the retro", "what should we encode from this ticket?", "post-impl retro", or "retro on PR #N". Also triggers after a review-tdd-green run finds gaps. The goal: surface 3–5 specific candidate additions to CLAUDE.md, issue templates, or hooks — not a comprehensive audit, just what's worth making permanent.
Actively test the engineer's understanding of a system — whether they built it, inherited it, or are reviewing it. Use when asked to "quiz me on [system]", "test my understanding of what we built", "quiz me before this PR", or "help me onboard to [system]". The narration technique applied to comprehension: the act of explaining forces the engineer to find where their understanding breaks down.