write-planlisted

# Write Plan Planning buys two things: smaller review units, and a decision about ordering made before anyone is committed to code. It buys nothing else, so the amount of it should track the work. A one-line fix that arrives with a five-phase checklist has cost more than it saved. ## Process 1. Check whether a plan for this task [already exists](references/persisted-plans.md) and continue it rather than starting a second one 2. Name the shape of the work and [route](#route-by-shape) to what you need 3. Load the skills that shape the plan's content: `write-code` for how the implementation should look, `write-tests` for what coverage the change needs 4. Gather context. Where the research spans genuinely independent areas that are too wide to cover yourself, use `orchestrate-investigation`; investigate directly otherwise 5. Draft the split and confirm it with the user, with options, before detailing each change 6. Present the plan using `assets/plan-artifact.html`, which is self-documenting: read it and fill in the placeholders rather than rebuilding it. Its open questions exist to grill the user on the approach, so ask enough per change to surface the decisions that would change the plan, and stop when further questions stop changing it 7. Iterate on the artifact until the user has no more feedback, gathering context again where their answers open something up 8. Hand over rather than implement: end referencing the plan locations so implementation starts on