skills.rest
inuishan
inuishanCOMMUNITY
Explore all skills by this author →
GitHub

product-capability

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

Updated Apr 7, 2026
Search Tags:#requirements#handoff#constraints#srs#prd#product spec#capability planning
One-click install
npx skills add https://github.com/inuishan/mac-storage-organiser --skill product-capability-inuishan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-capability
Source: https://github.com/inuishan/mac-storage-organiser/tree/main/.codex/skills/product-capability
Command: npx skills add https://github.com/inuishan/mac-storage-organiser --skill product-capability-inuishan

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 converts that intent into a durable, SRS-style capability plan that exposes invariants, interfaces, and unresolved decisions 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. - Structured Handoff: Produces a fixed output format (CAPABILITY, CONSTRAINTS, IMPLEMENTATION CONTRACT, NON-GOALS, OPEN QUESTIONS, HANDOFF) and points to the next execution lane. - Use Case: A cross-service feature request arrives as a vague roadmap note. Use this Skill to generate a capability manifest that separates fixed policy from open questions, so implementation can start without re-litigating assumptions in review. ## Quick Start Turn this PRD into an implementation-ready capability plan with explicit 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 sentence covering the user, the new capability, and the outcome change, then extract constraints like invariants, trust boundaries, and lifecycle transitions. Finish with an SRS-style contract listing actors, states, interfaces, and open questions blocking implementation.

What is a capability plan in product engineering?▼

A capability plan is a durable artifact that makes hidden product constraints explicit before implementation starts. It separates user-visible promises from implementation details and distinguishes fixed policy, architecture preferences, and unresolved decisions.

When should I write a capability contract before coding?▼

Write one when a feature crosses multiple services, repos, or teams, or when senior engineers keep restating the same hidden assumptions in review. It is most useful when product intent is clear but architecture, data, or policy implications are still fuzzy.

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

This approach does not invent product truth; unresolved questions must be marked explicitly rather than smoothed over. It also does not replace architecture review or product clarification when the handoff indicates those are needed first.

How do I handle conflicting constraints between a PRD and an existing repo?▼

State the conflict clearly instead of smoothing it over, and record which constraints are fixed policy versus open decisions. The capability artifact should flag the conflict as a blocker requiring product or architecture clarification before implementation.

Related Skills

Explore More Product & Management Skills→
WUIX69WUIX69

product-capability

Translate product intent into an implementation-ready capability plan with constraints and open questions.

Community
Advanced
narailabsnarailabs
10

connector-creator

Scaffold local narai-primitives connectors with gather() and action interfaces.

Official
Advanced
Pixel-Process-UGPixel-Process-UG
1

reverse-engineering-specs

Generate behavioral specifications from code by tracing paths, data flows, and state mutations.

Official
Advanced
ArtRivArtRiv

gsd-quick

Execute small ad-hoc tasks with atomic commits and STATE.md tracking.

Community
Intermediate