decomposing-feature-to-stories

Decompose feature specs into up to seven BSP-ordered atomic stories.

1|Updated Jan 6, 2026

Search Tags:#testing #spec-driven #outcomes #acceptance-criteria #story-spec #feature-decomposition #bsp-ordering

Ready to run

npx skills add https://github.com/outcomeeng/claude --skill decomposing-feature-to-stories-outcomeeng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decomposing-feature-to-stories
Source: https://github.com/outcomeeng/claude/tree/main/plugins/spx-legacy/skills/decomposing-feature-to-stories
Command: npx skills add https://github.com/outcomeeng/claude --skill decomposing-feature-to-stories-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaking down features into actionable, testable units by decomposing a feature into a limited set of atomic stories while preserving integration outcomes in the feature.

Core Features & Use Cases

Ensures features decompose into ≤7 atomic stories, each described by a clear outcome.
Keeps integration and quality-gate outcomes within the feature, moving only atomic outcomes to stories.
Provides BSP-based ordering guidance and a template for Story Specs with an Analysis section.

Quick Start

Read the feature spec in full, identify atomic outcomes, and create up to seven stories with BSP-based numbering.

Frequently Asked Questions about decomposing-feature-to-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I break down a feature spec into actionable user stories?▼

To break down a feature spec, identify atomic outcomes and move only those to individual stories while preserving integration outcomes in the feature. This ensures each story remains a single, testable implementation unit.

What is the maximum number of stories a feature should be decomposed into?▼

Feature decomposition caps the total at seven stories to maintain manageable scope. This limit ensures each story represents an atomic outcome that can be implemented as a single unit.

How do I order user stories using BSP dependencies?▼

Order user stories by applying BSP-based numbering to sequence story specs according to their dependencies. This generates a structured implementation order with clear references to BSP dependencies where applicable.

Should integration outcomes stay in the feature or move to individual stories?▼

Integration and quality-gate outcomes must remain in the feature spec. Only atomic outcomes are moved to individual stories to ensure integration logic is preserved at the feature level.

How do I write acceptance criteria for decomposed story specs?▼

Generate clear acceptance criteria for each story spec by defining its atomic outcome. Include an analysis section proving the decomposition approach to validate that each story can be implemented as a single unit.

What is the best way to ensure decomposed stories are testable units?▼

The best way to ensure testable units is to decompose features into atomic outcomes using a story spec template. This approach limits stories to seven and includes an analysis section validating the single-unit implementation capability.