write-planlisted

# Write plan Decompose an approved spec into tasks small and independent enough to execute one at a time, ordered so nothing starts before what it depends on exists. ## When to use Once a spec is signed off (and, when the change is architecturally significant, once the architect has defined boundaries/ADRs), or whenever the workflow reaches the Plan step. ## Method 1. **Slice to INVEST size.** Break the spec's requirements into tasks that are each Independent, Negotiable, Valuable, Estimable, Small, and Testable (Bill Wake). A task that can't be estimated or tested on its own is still too big — split it again before it goes in the plan. 2. **Order by dependency.** Group into phases (`##` headings) and sequence tasks so every dependency appears before what needs it — data/schema before the services that read it, services before the UI that calls them, cross-cutting infra before the features built on it. State a cross-task dependency explicitly in the task line or a short note, never leave it implicit. 3. **Write each task as a checkbox line** using the repo's task convention exactly: `- [ ] T-012 Title @owner ~level %status` - `T-012` — a stable, sequential task ID (never reused, never renumbered after creation). - `Title` — outcome-phrased, short enough to scan. - `@owner` — who/what role picks it up (`@dev`, `@qa`, agent name, or a person). - `~level` — size signal, one of `~quick` / `~standard` / `~major` — keep it Small by this skill's