understanding-outcome-decomposition

Capabilities, features, and stories represent distinct scopes in outcome decomposition, preventing level conflation. Capabilities define broad product areas, features break these into manageable units, and stories are atomic, testable implementation units.

Decompose a PRD by applying the Outcome Engineering framework to break high-level product goals into capabilities, features, and stories. Ensure each piece is well-defined, testable, and correctly sized through vertical slicing.

Avoid feature breakdown mistakes by recognizing pitfalls like placing story-level outcomes in features or treating ADRs as implementation tasks. Maintain clear definitions of scope and sizing at each decomposition level.

Vertical slicing is needed when decomposing outcomes into capabilities, features, and stories to ensure each unit delivers independent value. This structured approach guides agents in correctly breaking down work within the Product Tree structure.

Applying outcome decomposition without a structured framework risks conflating capabilities with stories and misdefining scope. The Outcome Engineering framework provides the necessary level semantics and decomposition guidance to ensure structured product development.

Treating ADRs as implementation tasks breaks feature breakdown because ADRs document architectural decisions, not actionable work units. Conflating them with stories or features disrupts the clear definitions of scope required for proper outcome decomposition.