decompose-spec

To turn a design spec into an actionable task graph, provide the design doc reference and use a decompose workflow to generate an explicit, executable graph with dependencies and blockers. A dry-run option previews the decomposition before materializing it.

The best way to preview a task graph before committing changes is using the dry-run option during decomposition. This generates a preview of the design-spec-derived graph and its dependencies without actually materializing the tasks into the workflow.

Yes, you can place decomposed tasks under an existing parent task by using optional parent and runtime controls during the decomposition process. This integrates the newly generated graph nodes directly into your existing work hierarchy.

To refine a task graph after initial decomposition, use standard task primitives like add, dep, doc, and update. These commands guide post-decomposition refinement to adjust dependencies, add documentation, and finalize a production-ready plan.

Spec-driven decomposition supports cross-functional team collaboration by converting a shared design doc into concrete tasks and explicit dependencies. This reduces ambiguity and manual planning, providing a clear, executable work breakdown structure for all team members.