decomposing-prd-to-capabilities

Decompose PRDs into capability specifications with BSP numbering.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeengineering/spx-claude --skill decomposing-prd-to-capabilities-outcomeengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decomposing-prd-to-capabilities
Source: https://github.com/outcomeengineering/spx-claude/tree/main/plugins/spx/skills/decomposing-prd-to-capabilities
Command: npx skills add https://github.com/outcomeengineering/spx-claude --skill decomposing-prd-to-capabilities-outcomeengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you break down complex Product Requirements Documents (PRDs) into manageable, well-defined capability specifications, ensuring a clear understanding of what the product should be able to do.

Core Features & Use Cases

  • Capability Identification: Guides you to identify distinct product abilities that are cross-cutting and vertical slices of functionality.
  • Structured Decomposition: Provides a framework for organizing these capabilities using a BSP (Base, Scale, Priority) numbering system to manage dependencies.
  • Use Case: When starting a new software project, you can use this Skill to take the high-level product vision from the PRD and map out the core capabilities like "User Authentication," "Data Storage," and "Reporting," ensuring a solid foundation before diving into feature-level details.

Quick Start

Use the decomposing-prd-to-capabilities skill to break down the attached product requirements document into distinct capabilities.

Frequently Asked Questions about decomposing-prd-to-capabilities

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

FAQPage Schema
How do I break down a PRD into manageable capabilities?

To decompose a PRD into capabilities, this Skill identifies cross-cutting vertical slices of functionality and organizes them into well-scoped capability specifications using BSP numbering for dependency management.

What is a capability specification in product management?

A capability specification defines what a product CAN DO by identifying distinct, cross-cutting vertical slices of functionality from a Product Requirements Document, ensuring a clear understanding of product abilities before feature-level development.

How does BSP numbering manage dependencies in product requirements?

BSP (Base, Scale, Priority) numbering provides a structured framework for organizing capabilities and managing their dependencies, supporting the organic growth of the capability tree as the product evolves.

When should I decompose product requirements into capabilities instead of features?

You should decompose product requirements into capabilities when starting a new software project to map the core product vision into foundational abilities like User Authentication or Data Storage before diving into feature-level details.

What is the best way to structure cross-cutting functionality in software architecture?

The best way to structure cross-cutting functionality is to identify vertical slices that define distinct product abilities, organizing them with a BSP numbering system to manage dependencies and support organic capability tree growth.