pipeline

Pipeline

Run the full lifecycle from idea to merged change. Every stage is gated; no auto-advance.

When to use

• "build X", "add Y", "ship Z", "implement <feature>"
• Any request that implies more than a one-line edit
• The user says "go end to end"

For a pure debugging session, single research question, or one-line edit, invoke the matching phase skill directly instead.

Tier classification (do first)

Classify scope before any stage runs.

Tier	Criteria	Stages run
micro	≤30 LOC, single file, no API change, no new dep	implement → verify → ship
small	≤300 LOC, ≤3 files, internal only, no schema/API change	All, no subagent reviewer
full	New API / schema / multi-module / external surface	All, with subagent reviewer

Default to the higher tier when borderline. State the chosen tier explicitly so the user can override.

Do NOT skip stages or downgrade ceremony without explicit user approval. Do NOT begin stage N+1 until stage N's gate passes.

Stages

#	Name	Skill	Output
1	Design	design	Spec doc
2	Plan	plan	Plan doc
3	Implement	implement (uses tdd)	Code + tests
4	Verify	verify	Pass / fail report
5	Review	review	Reviewed code
6	Ship	ship	PR / merge

Inter-stage gate

Between every stage:

1. Summarize stage N's output in 1-3 lines
2. Ask: "Proceed to stage N+1, revise stage N, branch to spike, or abandon?"
3. Wait for explicit confirmation. No auto-advance.

Stage invocation pattern

For each stage:

1. State entry: "Stage N: <name>. Invoking <skill>."
2. Invoke the skill via the Skill tool, passing context (tier, prior stage outputs)
3. On return, summarize the output
4. Run the inter-stage gate
5. Proceed, revise, spike, or abandon

Spike branch (any stage)

When uncertainty is too high to continue:

1. State the specific question the spike must answer
2. Set a time budget (LOC + hours)
3. Run a minimal exploratory implementation
4. Document findings
5. Return to the originating stage and revise

Abandon branch (any stage)

When the user opts out at any gate:

1. Commit work in progress with a status note
2. Update spec / plan to Status: abandoned if they exist
3. Exit cleanly. Do not run remaining stages.

Termination

The pipeline ends after ship returns. State the final status:

• Spec path
• Plan path
• PR URL (if applicable)
• Outstanding follow-ups
• Suggested next action