product-capability

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

Updated May 7, 2026
One-click install
npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill product-capability-mirzadham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-capability
Source: https://github.com/mirzadham/trainingroombookingsystem2/tree/main/.agent/.agents/skills/product-capability
Command: npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill product-capability-mirzadham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product intent from PRDs, roadmap notes, or founder discussions often stays implicit, forcing engineers to rediscover hidden constraints mid-implementation. This Skill turns that intent into an explicit, durable capability contract before multi-service work 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 Extraction: Surfaces 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, non-goals, and open questions, ending with a clear handoff decision. - Use Case: A cross-repo feature request arrives with only a PRD paragraph. Use this Skill to generate a capability manifest that exposes fixed policy, architecture preferences, and unresolved decisions before any code is written. ## 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, then extract constraints such as business rules, invariants, trust boundaries, and lifecycle transitions. Finish with an SRS-style contract covering actors, states, interfaces, non-goals, and open questions before implementation starts.

What is a capability contract in product planning?▼

A capability contract is a durable artifact that records what must be true before implementation: fixed policies, architecture preferences, data ownership, and unresolved decisions. It replaces scattered notes and senior-engineer memory with a reusable planning document.

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 write the actual implementation code?▼

No. It produces the capability plan and ends with an explicit handoff: ready for direct implementation, needs architecture review, or needs product clarification. Downstream lanes such as tdd-workflow or api-connector-builder handle execution.

What are the limitations of PRD-to-SRS planning?▼

The plan is only as good as the inputs; unresolved product questions must be marked explicitly rather than invented. It also does not replace architecture review for genuinely ambiguous cross-system decisions.