write-planlisted

# Write Plan Plan-phase entry skill. Convert an approved spec or a clear small goal into a concrete plan that another engineer (or specialist agent) can execute without re-asking the user. ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER start editing code before the plan names the files, the order, and the verification per task. 2. NEVER spawn more than one parallel agent on the same feature without a written cohesion contract that pins file ownership and merge order. 3. NEVER write a vague task like "add tests" — every task must name a test or evidence that proves it is done, AND the exact runnable command that checks it, so the build loop can verify the task without guessing. 4. Pick the simplest viable approach. Complexity needs an explicit reason and user awareness. </EXTREMELY-IMPORTANT> ## When to use - A spec exists and you are about to start implementation - A goal is small but touches more than one file - Multiple specialists may need to edit the same module - The work could be parallelized across worktrees or sessions Skip when: - The task is a one-line fix on a single file (just do it) - The user asks for a question / explanation only - The router tiered the task **R2** (1 file, clear scope, ≈≤30 logic lines) — the plan is a 3-5 line inline checklist in chat, each step with its verify command; no plan artifact. Scope grows past one file mid-flight → stop, write the real plan here. ## Boundary Owns: - HOW / WHO / WHERE / ORDER. - File list, task order, test plan