plan

Plan

Turn an approved spec into an implementation plan that an executor can run step by step.

Pre-conditions

• Spec exists at docs/specs/YYYY-MM-DD-<topic>.md (small / full tier) OR a 1-line design (micro tier)
• Status: approved
• Tier: micro | small | full

If pre-conditions aren't met, return immediately with status=missing_spec and the gap.

Micro tier

Skip the formal plan. State the change inline (file path, change summary, verification test). Return.

Small / full tier

Walk the spec sequentially:

1. Read the spec — state in one paragraph the chosen approach and the goals
2. Identify discrete units — each step should be:
   • One logical change (~20-150 LOC)
   • Independently testable
   • Self-contained enough to commit
3. Write the plan to docs/plans/YYYY-MM-DD-<topic>.md using plan-template.md
4. Test strategy — unit, integration, e2e split. Coverage target. Manual cases if applicable.
5. Rollback — for each step, how to revert it
6. Open questions — decisions deferred to implementation. State who decides and when.

Self-review

Before returning, check:

• Every spec requirement maps to ≥1 plan step
• Every plan step has a verification test
• Step ordering respects declared dependencies
• No step is so large it can't be tested independently

Fix inline.

Output

{
  "plan_path": "<path>",
  "steps": <count>,
  "spec_path": "<path>",
  "test_strategy": { "unit": "<>", "integration": "<>", "e2e": "<>" }
}

Handoff

Return control to the orchestrator. The orchestrator gates user approval before invoking implement.