product-capability

Convert PRD intent into implementation-ready capability plans with constraints and contracts.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill product-capability-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-capability
Source: https://github.com/diazMelgarejo/orama-system/tree/main/.cursor/.agents/skills/product-capability
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill product-capability-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product intent from PRDs, roadmap items, or founder notes often leaves engineering constraints implicit, causing senior engineers to repeatedly restate hidden assumptions during review. This Skill turns vague product intent into an explicit, durable capability contract before multi-service implementation begins. ## Core Features & Use Cases - Capability Restatement: Compresses the ask into one precise statement covering the user, the new capability, and the outcome change. - Constraint Resolution: Extracts business rules, invariants, trust boundaries, data ownership, lifecycle transitions, and rollout requirements that usually live only in senior-engineer memory. - SRS-Style Contract: Produces an implementation-facing plan with actors, surfaces, states, interfaces, data implications, security and policy constraints, and open questions. - Use Case: A cross-service feature request arrives as a PRD. Use this Skill to generate a capability manifest that separates fixed policy from open decisions, then hand off to architecture review or direct implementation. ## Quick Start Use the product-capability skill to turn this PRD into an implementation-ready capability plan with constraints, non-goals, and open questions.

Frequently Asked Questions about product-capability

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

FAQPage Schema
How do I turn a PRD into an implementation plan?

Restate the capability in one precise sentence covering the user, the new capability, and the outcome change. Then resolve constraints like invariants, trust boundaries, and lifecycle transitions, and produce an SRS-style contract with actors, interfaces, and open questions.

What is a capability contract in product planning?

A capability contract is an SRS-style artifact defining actors, surfaces, states and transitions, interfaces, data model implications, and security or policy constraints. It makes hidden engineering assumptions durable instead of relying on senior-engineer memory.

When should I use capability planning instead of writing code directly?

Use it when a feature crosses multiple services, repos, or teams, or when product intent is clear but architecture, data, or policy implications are still fuzzy. It prevents rediscovering hidden constraints mid-PR.

Does this skill work with existing product documentation?

Yes. If the repo has a durable product-context file such as PRODUCT.md, a docs/product directory, or a program-spec directory, the capability plan updates it there rather than creating a separate planning stack.

What are the limitations of PRD-to-SRS translation?

It does not invent product truth; unresolved questions are marked explicitly as blockers. If the request conflicts with existing repo constraints, the conflict is surfaced rather than smoothed over, and some items may require product clarification before implementation.