decompose

To break a spec-driven design into actionable tasks, you submit your proposal, spec, and design artifacts to Cortex and run the decompose process. It maps these inputs into executable work units with defined acceptance criteria and explicit dependencies.

You generate a task board for an orchestrator by feeding SDD artifacts into the decomposition pipeline, which produces a JSON task board compatible with the orchestrator TB API and persists it to Cortex under the sdd/{change-name}/tasks namespace.

Yes, you can execute SDD tasks in parallel because the decomposition process enforces acyclic dependencies and phase sequencing. This dependency ordering identifies work units that can run concurrently without blocking each other.

Yes, the SDD task decomposition pipeline supports optional openspec integration. This allows you to incorporate openspec alongside the standard proposal, spec, and design artifacts when generating your phased task board.

The best way to manage dependencies in a spec-driven development task board is to enforce acyclic dependencies during decomposition. This ensures phased, dependency-ordered tasks are structured correctly before persistence to Cortex.

SDD task decomposition requires proposal, spec, and design artifacts because these inputs map directly to executable work units with defined acceptance criteria. Without them, the pipeline cannot generate a phased, dependency-ordered task board.