This skill should be used when the orchestrator needs to "decompose", "create task graph", "break down design into units". Reads design artifacts, produces task graph with units, dependencies, and parallelism groups.
Read design artifacts, produce a task graph for autonomous implementation. Called once by the orchestrator after the design phase is complete.
Read .clawdance/design/DESIGN.md, .clawdance/design/STACK.md, and all files in
.clawdance/design/contracts/. Understand components, connections, tech stack, and
testing approach.
Each component/service/module is a candidate unit. A unit should be:
depends_on: which units must complete first (data model before API, etc.)parallel_group: units with same dependencies and no inter-dependency
get the same group name (executed via OMC team mode)For each unit:
contracts_read: contract files to read before implementingcontracts_produced: files this unit creates that others need.clawdance/design/contracts/.
If missing: STOP and report the gap. Do not guess.Create .clawdance/ with:
task-graph.yaml — units with all fields (id, name, description, depends_on, contracts_read, contracts_produced, parallel_group).
state.yaml — status: pending, all units in units_remaining.
constraints.yaml — seed with design-phase constraints if visible (things like "all services must use the same auth scheme"). Use this exact format: