mvt-decompose

Epic decomposition breaks large requirements into 2-8 right-sized child changes that can each go through analyze, design, implement, and review cycles. This reduces planning ambiguity and creates a clear execution sequence.

Dependency mapping defines a DAG of child changes to show sequencing, parallel work opportunities, and blockers. This approach helps teams identify explicit boundaries and a recommended starting point before implementation begins.

Workflow planning for multi-domain initiatives creates a workable decomposition plan instead of forcing everything into one oversized effort. It generates structured artifacts with unique change identifiers and project-aware guidance for downstream continuity.

Yes, epic planning produces both narrative and structured outputs as epic.md and epic.yaml files. These artifacts include unique change identifiers, DAG dependency checks, and session state updates for downstream workflow continuity.

You need epic decomposition when a requirement is too large to handle as a single change and needs explicit scope boundaries. It is essential for large initiatives requiring sequencing, child change definitions, and a clear starting point before detailed analysis.

Without epic decomposition, large initiatives suffer from planning ambiguity because they lack explicit dependency relationships and right-sized sub-changes. Breaking them into 2-8 child changes creates a DAG that defines sequencing and identifies blockers.