1.3 Task decomposition
1.3 Task decomposition
work is broken into bugs / features / epics / investigations as documents, not just tickets
Levels
Level 0
No structure
Level 1
Linear tickets only
Level 2
Structured doc-as-task with clear scope; each of at least `{investigation, feature, bug fix, tech research, spike}` has its own template with type-appropriate required fields (e.g. investigation templates include incident reference, reproduction steps, and timeline; feature templates include acceptance criteria and scope boundaries)
Level 3
Past task structures inform new task templates; templates improve with use — template drift is tracked, recurring shapes produce reusable templates, and the template set itself evolves (new types added, stale ones deprecated)