decomposing-capability-to-features

To break down a capability into features, you isolate significant vertical slices that can be realized independently. This ensures each feature has clear boundaries and can be implemented incrementally.

The maximum number of stories allowed per feature is seven atomic stories. This constraint ensures features remain focused, well-scoped, and manageable for implementation teams.

You establish dependency ordering by applying BSP-based sequencing to the decomposed features. This enforces proper integration outcomes and moves atomic outcomes to stories in the correct logical order.

No, if a vertical slice requires more than seven stories, it must be further decomposed. The skill enforces a seven-story maximum to guarantee features are properly scoped for incremental implementation.

The best way to scope a feature is to read the capability spec completely and isolate a single vertical slice. This produces feature specs with clear boundaries, outcomes, and defined test strategies.

Feature decomposition enforces integration outcomes to ensure each atomic story contributes to a cohesive feature. This guarantees that vertical slices deliver functional value and pass defined test strategies upon implementation.