spec-planlisted

# Plan a Spec Turn requirements into a plan a cold-context session can execute without re-discovering the project. The requirements say *what and why*; the plan says *how*, in the repository's own terms - which sibling to copy, which rule to re-read, and what to run to know a step is done. Every intake ends here: `spec-pull` for a tracker item, `spec-create` for a change no tracker item covers. Both write `NNN-requirements.md` and hand over; this skill writes `NNN-plan.md` beside it. A plan already present means re-planning - re-read it, apply the delta, and keep the ticked work steps that still hold. An open question does not stop this skill: **a question blocks execution, never planning** (`spec-discipline`). The plan is written with the question standing in it. ## Steps 1. **Read before writing** - the plan's quality is set here, not in the prose: - `NNN-requirements.md` end-to-end, including its captured source and decision log. - The feature doc for the touched area, the project rules the change might contradict (rules win - flag the conflict now, never plan around it), and the decision records. - The closest **shipped** sibling spec, end-to-end: it is the structural template. No sibling and no profile - use the default and say so out loud. 2. **Write `NNN-plan.md`** into the spec folder, carrying the folder's number. Sections, in order: - **`## Requirements coverage`** - the first section, always. A table mapping every requirement to the step that deliv