Task Decomposition

Convert a technical design into a set of actionable tasks and a persistent decomposition document. The input is a technical design with affected components, sequencing, and scope boundaries. The output is a task hierarchy that any developer or agent can pick up and execute without further clarification.

Purpose

A technical design describes what changes at the component level — but components aren't work items. Decomposition slices the design into assignable, estimable, trackable units with explicit boundaries, ordering, and completion criteria. The decomposition document persists these decisions so any implementer — human or agent — can pick up unblocked work without further clarification.

When to Decompose

Decompose when the technical design touches multiple components, involves multiple implementers, takes more than a day, or has non-obvious ordering constraints. Skip when a single task with acceptance criteria covers the entire scope.