product-capability

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

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill product-capability-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-capability
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/product-capability
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill product-capability-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product intent from PRDs, roadmap notes, or founder discussions often leaves engineering constraints implicit, causing senior engineers to repeatedly restate hidden assumptions during review. This Skill turns vague product asks into an explicit, durable capability contract before multi-service implementation begins. ## Core Features & Use Cases - Capability Restatement: Compresses a product 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 a structured implementation contract with actors, surfaces, states, interfaces, data model implications, policy constraints, and open questions. - Use Case: A founder shares a roadmap note for a booking feature spanning multiple services. Use this Skill to produce a capability manifest that exposes fixed policies, unresolved decisions, and a clear handoff before any coding starts. ## 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 statement, then resolve constraints like business rules, invariants, and data ownership before defining the implementation contract. This Skill produces an SRS-style plan with actors, states, interfaces, and open questions blocking implementation.

What is a capability contract in product planning?▼

A capability contract is an SRS-style artifact defining the capability summary, non-goals, actors, surfaces, state transitions, interfaces, data model implications, and 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, lifecycle, or policy implications are still fuzzy. It is not needed for single-service changes with obvious constraints.

Does this Skill invent product decisions that are still unresolved?▼

No. The Skill explicitly marks unresolved questions instead of inventing product truth, and separates fixed policy from architecture preference and open decisions. Conflicts with existing repo constraints are called out clearly.

Where should the capability artifact be stored in a repo?▼

If the repo has a durable product-context file such as PRODUCT.md, docs/product/, or a program-spec directory, update it there. Otherwise create a capability manifest using the template at docs/examples/product-capability-template.md.