planlisted

# Planning Requirements say what must be true. A plan says **who makes it true, in what order, and how anyone will know.** It is not a schedule — it is a set of contracts small enough that one worker can hold one. ## What a task is One file, `devteam/tasks/T-n.md`, from `${CLAUDE_PLUGIN_ROOT}/templates/tasks/TASK.md`. Six things, none optional: | Field | And what makes it wrong | |---|---| | **Discharges** | the `R-n` it makes true. **A task discharging none is scope creep, or a requirement nobody wrote down** — and the check will say so (P-4) | | **Scope** | the paths it may write. Too wide and it collides with its neighbours; too narrow and it escalates mid-flight. Both are your error, not the worker's | | **Depends on** | tasks that must be `DONE` first. A named task, never "after the backend" | | **Gate** | what must be **true** afterwards — a condition, not a feeling | | **Verify** | the exact command that proves the gate, decided **now**, before anyone is invested in passing it — and **scoped to this task's own files**, because at any width above one a whole-suite command measures other tasks' half-finished work and fails for reasons that have nothing to do with this one | | **Estimate** | tokens and minutes. Wrong is fine; absent is not, because an estimate never compared to a measurement stays wrong forever (P-41) | **A gate phrased over the whole project is a gate over everybody else's in-flight work.** `pytest -q` expecting an unchanged count is a fine gate at