skills.rest
simonheimlicher
simonheimlicherCOMMUNITY
Explore all skills by this author →
Website𝕏@simonheimlicherGitHub

decomposing-capability-to-features

Transform capabilities into structured feature specs with BSP-ordered sequencing and seven-atomic-story limits.

1|Updated Jan 6, 2026
Search Tags:#planning#decomposition#product-management#capability#feature-spec#vertical-slice#story-based
One-click install
npx skills add https://github.com/simonheimlicher/spx-claude --skill decomposing-capability-to-features
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decomposing-capability-to-features
Source: https://github.com/simonheimlicher/spx-claude/tree/main/plugins/spx/skills/decomposing-capability-to-features
Command: npx skills add https://github.com/simonheimlicher/spx-claude --skill decomposing-capability-to-features

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams convert high-level capabilities into well-scoped feature specs. It ensures that each feature can be implemented as a vertical slice within a small number of atomic stories, enabling predictable delivery and better roadmapping.

Core Features & Use Cases

  • Vertical-slice decomposition: Breaks down capabilities into significant, independently valuable features.
  • 7-story discipline: Each feature is designed to be implementable in at most seven atomic stories.
  • BSP-aware sequencing: Helps order features by dependencies to minimize rework.
  • Use Case: Start from a capability like "User Authentication" and derive 1-3 features that collectively cover the capability, each bounded by seven stories.

Quick Start

  1. Read the capability spec completely.
  2. Identify a feasible vertical slice that can be implemented in ≤7 stories.
  3. Create a feature spec with BSP-based numbering and a defined boundary.
  4. Validate that the feature does not overlap with siblings and that the scope can grow organically.

Frequently Asked Questions about decomposing-capability-to-features

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

FAQPage Schema
How do I break down a product capability into manageable features?▼

Decomposing a capability into manageable features involves identifying vertical slices that deliver independent value. This approach breaks capabilities like User Authentication into 1-3 bounded features, each implementable within seven atomic stories to ensure predictable delivery.

What is a vertical slice in feature decomposition?▼

A vertical slice in feature decomposition is a significant, independently valuable piece of a capability. It cuts across architectural layers to deliver end-to-end user value, ensuring each feature spec remains focused and can grow organically without overlapping sibling features.

How many stories should a feature spec contain?▼

A feature spec should contain a maximum of seven atomic stories. This discipline keeps scope manageable and ensures the feature can be implemented predictably, enabling better roadmapping and minimizing rework during product development.

How do I sequence feature specs by dependencies?▼

Sequencing feature specs by dependencies uses BSP-aware ordering to minimize rework. This method assigns BSP-based numbering to each feature, ensuring foundational components are built first so subsequent features can grow organically without structural conflicts.

When should I use capability decomposition for product planning?▼

Use capability decomposition for product planning when converting high-level capabilities into well-scoped feature specs. It is ideal for teams needing predictable delivery and better roadmapping through bounded, vertical-slice features with clear boundaries.

How do I validate boundaries between decomposed features?▼

Validating boundaries between decomposed features requires checking that no feature overlaps with its siblings and that scope can grow organically. Each feature spec must have a defined boundary and BSP-based numbering to ensure clean separation.

Related Skills

Explore More Product & Management Skills→
eugenelimeugenelim
15

frame-intent

Shape requests into level-tagged product intents with outcomes and assumptions.

Community
Advanced
ydnikolaevydnikolaev
8

product-analyst

Translate product vision into user stories, requirements, and roadmaps.

Community
Advanced
outcomeengoutcomeeng
1

decomposing-capability-to-features

Decompose capabilities into features with vertical slices and BSP ordering.

Official
Advanced
oakossoakoss
14

tracer-bullets

Implement features as verified vertical end-to-end slices across application layers.

Official
Intermediate