Workflow

Interactive pipeline guide. Shows current project state, suggests the next step, and routes to the correct stage orchestrator or skill.

Artifact Detection

Phase grouping: Files sharing the same NN prefix belong to the same phase.

Display Format

Stage 1 — Product Discovery              → /product
  {check} Manifesto     {path or "not found"}
  {check} PRD           {path} ({status})
  {check} Architecture  {path} ({status})

Stage 2 — Specification                   → /specification {NN}
  Phase {NN} ({name from plan title}):
    {check} Plan        {path} ({status})
    {check} Research    {count} doc(s) in docs/research/{NN}-*
    {check} Spec        {path} ({status})
    {check} Beads       {epic_id} ({completed}/{total} complete)

Stage 3 — Implementation                  → /implementation {NN}
  Phase {NN}:
    {progress} {completed}/{total} tasks complete
    Ready:       {list of ready task IDs}
    In progress: {list of in-progress task IDs}
    Blocked:     {count}

Where {check} is:

• [done] — artifact exists and is APPROVED/complete
• [exists] — artifact exists but not yet APPROVED
• [missing] — not found
• [warning] — missing but a later step was already done (skipped step)</on-state>

1. If no PRD → suggest /product or /requirements
2. If PRD but no Architecture → suggest /product or /architecture
3. If Architecture APPROVED but no Plan for current phase → suggest /specification {NN} or /plan
4. If Plan but no Research → suggest /specification {NN} or /research
5. If Research but no Spec → suggest /specification {NN} or /spec
6. If Spec but no Beads → suggest /specification {NN} or /tasks
7. If Beads exist → suggest /implementation {NN} or /investigate with ready tasks

When suggesting, present both the orchestrator (guided flow) and the direct skill (quick jump):

Next step: Research (Phase 01)
  Guided:  /specification 01  — walks through remaining steps
  Direct:  /research          — jump straight to research

• product → Skill(skill="product")
• specification → Skill(skill="specification") — ask for phase number if not provided
• implementation → Skill(skill="implementation") — ask for phase number if not provided</on-step>

Prerequisite map:

If prerequisites are unmet, warn but do not block:

Warning: You are about to run /spec but the following prerequisites are missing:
  - Research: no docs found in docs/research/{NN}-*

Without validated research, the spec will be based on unvalidated assumptions
from the plan. This historically causes task drift during implementation.

Do you want to:
  1. Run /research first (recommended)
  2. Proceed to /spec anyway
  3. Cancel

If user confirms → dispatch: Skill(skill="{skill-name}") </on-step>

Do NOT dispatch agents directly — always go through the corresponding skill or orchestrator so prerequisites are checked. </on-next>