Task Breakdown

Split large work into ordered, testable subtasks so it can be done incrementally and tracked.

Why this matters: Vague tasks lead to rework and "I thought you meant X." Clear, small subtasks with acceptance criteria mean anyone (human or agent) can pick one up, do it, and verify it without guessing. The team spends less time in sync meetings and more time shipping.

When to Activate

• User asks to "break down", "split into tasks", "create subtasks", or "plan this feature"
• Planning an epic, feature, or refactor for a sprint or backlog
• Preparing tickets for implementation (by human or agent)
• When scope is unclear and needs structure before coding

Work Process