Splitting work into tasks

DISRESPEC-SPINE: One fact once. No filler, repeated source material, empty sections, or chat restatement; after successful creation return only clickable artifact links, except for blockers, failed creation, incomplete verification, or irreversible-action confirmation.

Most work is one spec → one implementer — no task packet; the implementer fills the spec's ## Execution section. Cut tasks only when a spec has multiple independently dispatchable parallel/context slices, or a change plan defines separately dispatchable sequenced waves. Size alone does not create a task packet. The output is a set of self-contained task packets plus a few lines recording the order they run in.

Before cutting tasks, open references/task-packet.md and instantiate one copy per slice. Fill every placeholder from the controlling spec or change plan; do not reconstruct the packet shape from memory.