Product Capability
This skill turns product intent into explicit engineering constraints.
Use it when the gap is not "what should we build?" but "what exactly must be true before implementation starts?"
When to Use
- A PRD, roadmap item, discussion, or founder note exists, but the implementation constraints are still implicit
- A feature crosses multiple services, repos, or teams and needs a capability contract before coding
- Product intent is clear, but architecture, data, lifecycle, or policy implications are still fuzzy
- Senior engineers keep restating the same hidden assumptions during review
- You need a reusable artifact that can survive across harnesses and sessions
Canonical Artifact
If the repo has a durable product-context file such as PRODUCT.md, docs/product/, or a program-spec directory, update it there.
If no capability manifest exists yet, create one using the template at:
docs/examples/product-capability-template.md
The goal is not to create another planning stack. The goal is to make hidden capability constraints durable and reusable.
Non-Negotiable Rules
- Do not invent product truth. Mark unresolved questions explicitly.
- Separate user-visible promises from implementation details.
- Call out what is fixed policy, what is architecture preference, and what is still open.
- If the request conflicts with existing repo constraints, say so clearly instead of smoothing it over.
- Prefer one reusable capability artifact over scattered ad hoc notes.
Inputs
Read only what is needed:
- Product intent
- issue, discussion, PRD, roadmap note, founder message
- Current architecture
- relevant repo docs, contracts, schemas, routes, existing workflows
- Existing capability context
PRODUCT.md, design docs, RFCs, migration notes, operating-model docs
- Delivery constraints
- auth, billing, compliance, rollout, backwards compatibility, performance, review policy
Core Workflow
1. Restate the capability
Compress the ask into one precise statement:
- who the user or operator is
- what new capability exists after this ships
- what outcome changes because of it
If this statement is weak, the implementation will drift.
2. Resolve capability constraints
Extract the constraints that must hold before implementation:
- business rules
- scope boundaries
- invariants
- trust boundaries
- data ownership
- lifecycle transitions
- rollout / migration requirements
- failure and recovery expectations
These are the things that often live only in senior-engineer memory.
3. Define the implementation-facing contract
Produce an SRS-style capability plan with:
- capability summary
- explicit non-goals
- actors and surfaces
- required states and transitions
- interfaces / inputs / outputs
- data model implications
- security / billing / policy constraints
- observability and operator requirements
- open questions blocking implementation
4. Translate into execution
End with the exact handoff:
- ready for direct implementation
- needs architecture review first
- needs product clarification first
If useful, point to the next ECC-native lane:
project-flow-ops
workspace-surface-audit
api-connector-builder
dashboard-builder
tdd-workflow
verification-loop
Output Format
Return the result in this order:
CAPABILITY
- one-paragraph restatement
CONSTRAINTS
- fixed rules, invariants, and boundaries
IMPLEMENTATION CONTRACT
- actors
- surfaces
- states and transitions
- interface/data implications
NON-GOALS
- what this lane explicitly does not own
OPEN QUESTIONS
- blockers or product decisions still required
HANDOFF
- what should happen next and which ECC lane should take it
Good Outcomes
- Product intent is now concrete enough to implement without rediscovering hidden constraints mid-PR.
- Engineering review has a durable artifact instead of relying on memory or Slack context.
- The resulting plan is reusable across Claude Code, Codex, Cursor, OpenCode, and ECC 2.0 planning surfaces.
1---2name: product-capability3description: Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.4metadata:5 source: https://skillmd.com/skills/mhassan0000/product-capability6 origin: ECC7---89# Product Capability1011This skill turns product intent into explicit engineering constraints.1213Use it when the gap is not "what should we build?" but "what exactly must be true before implementation starts?"1415## When to Use1617- A PRD, roadmap item, discussion, or founder note exists, but the implementation constraints are still implicit18- A feature crosses multiple services, repos, or teams and needs a capability contract before coding19- Product intent is clear, but architecture, data, lifecycle, or policy implications are still fuzzy20- Senior engineers keep restating the same hidden assumptions during review21- You need a reusable artifact that can survive across harnesses and sessions2223## Canonical Artifact2425If the repo has a durable product-context file such as `PRODUCT.md`, `docs/product/`, or a program-spec directory, update it there.2627If no capability manifest exists yet, create one using the template at:2829- `docs/examples/product-capability-template.md`3031The goal is not to create another planning stack. The goal is to make hidden capability constraints durable and reusable.3233## Non-Negotiable Rules3435- Do not invent product truth. Mark unresolved questions explicitly.36- Separate user-visible promises from implementation details.37- Call out what is fixed policy, what is architecture preference, and what is still open.38- If the request conflicts with existing repo constraints, say so clearly instead of smoothing it over.39- Prefer one reusable capability artifact over scattered ad hoc notes.4041## Inputs4243Read only what is needed:44451. Product intent46 - issue, discussion, PRD, roadmap note, founder message472. Current architecture48 - relevant repo docs, contracts, schemas, routes, existing workflows493. Existing capability context50 - `PRODUCT.md`, design docs, RFCs, migration notes, operating-model docs514. Delivery constraints52 - auth, billing, compliance, rollout, backwards compatibility, performance, review policy5354## Core Workflow5556### 1. Restate the capability5758Compress the ask into one precise statement:5960- who the user or operator is61- what new capability exists after this ships62- what outcome changes because of it6364If this statement is weak, the implementation will drift.6566### 2. Resolve capability constraints6768Extract the constraints that must hold before implementation:6970- business rules71- scope boundaries72- invariants73- trust boundaries74- data ownership75- lifecycle transitions76- rollout / migration requirements77- failure and recovery expectations7879These are the things that often live only in senior-engineer memory.8081### 3. Define the implementation-facing contract8283Produce an SRS-style capability plan with:8485- capability summary86- explicit non-goals87- actors and surfaces88- required states and transitions89- interfaces / inputs / outputs90- data model implications91- security / billing / policy constraints92- observability and operator requirements93- open questions blocking implementation9495### 4. Translate into execution9697End with the exact handoff:9899- ready for direct implementation100- needs architecture review first101- needs product clarification first102103If useful, point to the next ECC-native lane:104105- `project-flow-ops`106- `workspace-surface-audit`107- `api-connector-builder`108- `dashboard-builder`109- `tdd-workflow`110- `verification-loop`111112## Output Format113114Return the result in this order:115116```text117CAPABILITY118- one-paragraph restatement119120CONSTRAINTS121- fixed rules, invariants, and boundaries122123IMPLEMENTATION CONTRACT124- actors125- surfaces126- states and transitions127- interface/data implications128129NON-GOALS130- what this lane explicitly does not own131132OPEN QUESTIONS133- blockers or product decisions still required134135HANDOFF136- what should happen next and which ECC lane should take it137```138139## Good Outcomes140141- Product intent is now concrete enough to implement without rediscovering hidden constraints mid-PR.142- Engineering review has a durable artifact instead of relying on memory or Slack context.143- The resulting plan is reusable across Claude Code, Codex, Cursor, OpenCode, and ECC 2.0 planning surfaces.