decompose-intent

To break down a validated product intent into buildable slices, you recursively decompose the intent one level at a time into child intents or shippable leaf specs. This ensures the planning tree remains honest and actionable.

Splitting features for tracker projection without skipping levels requires cutting leaf work by shippability rather than by component. This approach allows each slice to ship and test independently while maintaining parent intent backlinks.

Recursive intent decomposition works by applying a step-by-step scale-aware projection to capability, feature, and leaf-level planning. It requires a surviving riskiest assumption and records the decomposition rationale to generate tracker-ready projections.

Yes, you can use this intent decomposition approach with Jira Align, Linear, or markdown workflows. It supports tracker projection by transforming leaf-level intents into briefs or per-component slices formatted for your specific target scale.

You need a surviving riskiest assumption for feature decomposition when moving from a de-risked intent to the next actionable level. This prerequisite ensures the decomposition rationale is backed by validated hypotheses before generating shippable specs.

Decomposing leaf work by shippability instead of by component layer ensures each slice can ship and test on its own. This prevents incomplete feature fragments and maintains an honest, buildable product planning tree.