breakdown

To convert an approved design into executable tasks, you provide the design document to generate a structured breakdown with sequential task groups and per-agent documents for build agents.

Design-to-task conversion transforms approved designs into concrete, step-by-step execution breakdowns. You need it when preparing complex deployment workflows for automated build agents.

Yes, the task breakdown process generates categorized task groups with explicit dependencies, allowing parallel execution by build agents when possible.

To map design decisions to build agent actions, the breakdown generates execution documents that reference the Claude execution template and output structured per-agent documents for traceability.

No, the design-to-task breakdown process operates without external dependencies or components, requiring only the approved design document as input to generate execution breakdowns.

The best way to structure per-agent documents is generating them within organized PROCESS_DOCS/breakdowns directories using the feature name, ensuring explicit dependencies and execution template references are included.