skills.rest
outcomeengineering
outcomeengineeringOFFICIAL
Explore all skills by this author →
GitHub

decomposing-feature-to-stories

Decompose feature specifications into atomic stories with dependency-based BSP ordering.

1|Updated Jan 6, 2026
Search Tags:#product management#user stories#agile development#requirements engineering#feature decomposition#story writing
One-click install
npx skills add https://github.com/outcomeengineering/spx-claude --skill decomposing-feature-to-stories-outcomeengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decomposing-feature-to-stories
Source: https://github.com/outcomeengineering/spx-claude/tree/main/plugins/spx/skills/decomposing-feature-to-stories
Command: npx skills add https://github.com/outcomeengineering/spx-claude --skill decomposing-feature-to-stories-outcomeengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps break down large, complex features into smaller, manageable, and atomic user stories, ensuring a clear path for implementation and testing.

Core Features & Use Cases

  • Outcome Decomposition: Analyzes feature outcomes and categorizes them as either integration-level (to keep in the feature) or atomic (to move to stories).
  • Story Atomicity Verification: Ensures each identified story represents a single, coherent implementation unit with clear acceptance criteria.
  • Story Limit Enforcement: Guides the process to adhere to the recommended maximum of 7 stories per feature, prompting feature splitting when necessary.
  • BSP Ordering Guidance: Provides a strategy for ordering stories based on dependencies using BSP (Backlog, Sprint, Production) numbering.
  • Use Case: When a product manager defines a new feature like "User Profile Management," this Skill can be used to break it down into specific stories such as "Create User Profile," "Edit User Profile," "View User Profile," and "Delete User Profile," each with defined outcomes and acceptance criteria.

Quick Start

Use the decomposing-feature-to-stories skill to break down the 'User Authentication' feature into atomic stories.

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 into actionable user stories?▼

Feature decomposition involves identifying atomic outcomes within a feature specification and moving them into individual user stories. This ensures each story is an implementable, coherent unit with structured outcomes and clear acceptance criteria.

What is the maximum number of user stories per feature in agile development?▼

The recommended maximum is seven user stories per feature. If decomposition identifies more atomic outcomes, you should split the original feature into smaller features to maintain manageable implementation scopes.

How are user stories ordered based on dependencies?▼

Stories are ordered using BSP (Backlog, Sprint, Production) numbering. This strategy guides the implementation sequence by mapping story dependencies to ensure a logical path to production.

When should I keep an outcome at the feature level instead of moving it to a story?▼

Outcomes categorized as integration-level should remain in the feature specification. Only atomic outcomes, representing single coherent implementation units, are moved to individual stories.

How do I verify story atomicity when decomposing requirements?▼

Verify story atomicity by checking that each story represents a single, coherent implementation unit. The process ensures every story has structured outcomes and defined acceptance criteria before implementation.

Does feature decomposition work for complex product management specifications?▼

Yes, feature decomposition is designed to break large, complex product management specifications into smaller, manageable stories. It analyzes feature outcomes to ensure a clear path for implementation and testing.

Related Skills

Explore More Product & Management Skills→
lionbenjaminlionbenjamin
15

specify

Draft product specifications with problem, goals, user stories, and acceptance criteria.

Community
Intermediate
kazdenckazdenc
42

stories

Generate job stories and acceptance criteria from product requirements.

Community
Intermediate
Razmik-KutinavaRazmik-Kutinava

User Story Generator Expert

Generate agile user stories with acceptance criteria, priority, and story points.

Community
Intermediate
simonheimlichersimonheimlicher
1

decomposing-feature-to-stories

Decompose Feature specs into atomic Gherkin Story scenarios with ≤7 stories and BSP ordering.

Community
Basic