decompose-plan

Decomposing an implementation plan into Claude Code tasks requires parsing H2 Task headers within the plan file. The skill converts each Task N header into a distinct task while preserving the original plan content as the source of truth.

The required markdown structure uses H2 headers formatted as Task N with H3 Step sub-headers. The skill parses these specific headers to generate one execution-ready Claude Code task per plan task.

Dependency chaining enforces a linear sequence where Task N blocks Task N+1 during execution. This ensures tasks execute in the intended order specified by the decomposed plan headers.

Yes, you need jact to extract headers and TaskCreate tooling to create tasks. The skill requires jact to parse the plan headers and generate the corresponding Claude Code tasks.

Yes, tasks reference the original plan via jact rather than copying content. The plan remains the source of truth, ensuring traceability and preventing content duplication across generated tasks.

Use plan decomposition at execution start when you have a multi-step plan with Task N headers. It supports automation and traceability by converting structured plans into execution-ready tasks.