decompose-task

Parallel task decomposition splits approved build requests into named subcomponents and orchestrates parallel implementation execution. It delegates planning to a task-decomposer and dispatches component-coder work per plan item to reduce missed integration seams.

You need task decomposition for build requests when working on non-trivial artifacts that have clear architectural seams and working-set needs justifying the overhead. It requires explicit user approval like "let's build" or "ship it" to trigger the orchestrated execution workflow.

To verify interface contracts after parallel implementation, validate that outputs match interface and domain contracts, then perform stage 2 integration checks. This contract verification workflow ensures the decomposed subcomponents function correctly as a unified artifact.

Do not use task decomposition for bug fixes, doc-only edits, pure Q&A, or explicit user opt-outs. It applies strictly to create, implement, and build workflows for non-trivial artifacts that require parallel dispatch and integration verification.

The best way to orchestrate parallel implementation is delegating planning to a task-decomposer, dispatching component-coder subagents per plan item, updating plan.todo lifecycle states, and enforcing approval gates to ensure controlled execution and contract verification.