plan

§ 01 · purpose

Purpose

Turns a finished design into phases sized for one verification loop each, with the success criteria that prove a phase is done. The plan is the contract implement executes against — no rediscovery, no re-deciding architecture mid-build.

§ 02 · when to use

When to use it

• You have a design artifact and want it broken into runnable phases.
• Phases need to be parallel-marked so multiple worktrees can advance concurrently.
• The change is large enough that a single "implement everything" pass would be too coarse to verify.
• Skip in favor of blueprint when mid-flight micro-checkpoints between phases matter — blueprint collapses design + plan into a single iterative pass.

§ 03 · inputs

Inputs

design artifact

All architectural decisions must be settled; if Open Questions remain, plan stops and returns to design.

§ 04 · outputs

Outputs

§ 05 · key steps

Key steps

1. 01 Read the design artifact fully Why: Architecture · File Map · Ordering Constraints · Verification Notes are the only valid phasing inputs. Anything not in the design is out of scope for this pass — re-evaluation would break the design's authority.
2. 02 Decompose into worktree-sized phases Why: Each phase must compile and pass tests independently, touch ~3–8 files, group coherent file changes together, and follow the design's ordering constraints. Independent phases are explicitly marked parallel so multiple worktrees can advance concurrently.
3. 03 Confirm phase structure with the developer Why: Phase count and granularity are checked *before* code blocks are written. Catches split/merge corrections cheaply — fixing structure after fill is expensive.
4. 04 Write skeleton, then fill code per phase via Edit Why: Skeleton-first guarantees structural decisions happen up-front; per-phase Edit calls insert before/after code blocks from the design without rewriting prior phases. Lets long plans stream cleanly.
5. 05 Attach success criteria to every phase Why: Each phase carries - [ ] checkboxes that implement and validate re-run. The criteria are what mean "done" — the plan's verification contract.

§ 06 · related skills

Related skills