strategic-planning

Task decomposition breaks epics into actionable tasks and beads with mapped dependencies to guide execution. This reduces ambiguity and creates clear execution paths before any code is written during feature planning or architectural decisions.

Mapping task dependencies requires decomposing multi-step work into beads and explicit tasks. By validating the plan with an auditor and generating implementation artifacts, you produce a clear roadmap with milestones, risks, and resource needs.

Task decomposition suits cross-team coordination and architectural decisions by generating implementation plans that align work. It breaks down epics into tasks with dependencies to keep work coordinated across teams and milestones.

Validating an implementation plan involves explicit task breakdown, dependency mapping, and beads creation. The plan must be reviewed by a plan-auditor to ensure a clear execution path is established before building new components.

Strategic planning is needed when feature planning involves multi-step development work requiring task decomposition. It generates implementation plans mapping to milestones and risks, reducing ambiguity and guiding execution before coding begins.

Task decomposition works without external dependencies, operating independently to decompose development work into beads and tasks. It generates implementation artifacts and validates execution paths internally using a plan-auditor.