decomposing-prd-to-capabilities

Decompose PRDs into BSP-ordered capability specs with defined boundaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaking down a PRD into discrete, cross-cutting capabilities to enable scalable, modular product planning and clear ownership.

Core Features & Use Cases

  • Identify what the product CAN DO as standalone capabilities with well-defined boundaries.
  • Organize capabilities under BSP order to reveal dependencies and growth paths.
  • Start with a small, realizable capability and expand organically as needed.

Quick Start

Create a PRD, then apply a capability decomposition pass to produce a BSP-ordered capability map.

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 decompose a PRD into capabilities for product engineering?

PRD decomposition breaks product requirements into standalone, cross-cutting capabilities with well-defined boundaries to guide modular product engineering and clear ownership.

What is BSP ordering in product management capability mapping?

BSP ordering organizes decomposed capabilities to reveal dependencies and growth paths, enabling scalable product planning by mapping capabilities to a structured sequence.

Can I apply capability decomposition to varying PRD sizes?

Yes, capability decomposition applies to PRDs of varying sizes, allowing you to start with a small, realizable capability and expand organically as needed.

What is the best way to structure cross-cutting capabilities from product specifications?

Structuring cross-cutting capabilities involves defining clear boundaries and naming conventions, then mapping them to BSP orderings to ensure reusable capability specs and scalable growth.

How do I define capability boundaries when breaking down a PRD?

Defining capability boundaries requires identifying what the product can do as standalone functions, applying naming conventions, and establishing BSP orderings to produce reusable capability specifications.

Why should I use capability decomposition instead of direct feature planning?

Capability decomposition enables modular product planning and clear ownership by organizing standalone capabilities under BSP order, revealing dependencies and organic growth paths rather than rigid feature lists.