Split Into Tasks

Require docs/specs/<slug>/spec.md; if it is missing, stop before proposing tasks.

Read the spec, current code, relevant project decisions, glossary, and approved prototype. Treat missing implementation as work to do and conflicting sources as decisions to resolve. Keep one coherent deliverable as the spec itself.

Draft the fewest tracer-bullet tasks. Each task must deliver a complete, independently usable and verifiable path through every layer it touches. Put preparation in the first task that makes it useful, and declare only blockers that genuinely prevent a dependent outcome. Size tasks by delivered outcomes, not predicted context length or technical layers.