Product Capability

Transform a product requirement or feature request into a capability specification: a structured technical document that bridges product intent and engineering implementation.

Distinct from create-prd:

• create-prd → what and why (Jobs-to-be-Done, personas, scope). Audience: PMs, stakeholders.
• product-capability → what + how (acceptance criteria, task breakdown, traceability). Audience: engineers building it.

When to Use

• Engineering needs a clear, testable spec to implement from — not a narrative PRD
• Acceptance criteria must be explicit and verifiable before a ticket is created
• Traceability is required: feature request → capability → AC → implementation tasks
• A PRD exists but lacks the implementation detail engineers need to estimate or build

When NOT to Use