Skip to main content
Agent skill

Product Capability

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.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Product Capability when an AI agent needs a reusable SKILL.md workflow for this job: 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.

When not to use it

Skip Product Capability when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/product-capability
# Save SKILL.md to ~/.claude/skills/product-capability/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/product-capability/SKILL.md. For a shared project, commit the folder at .claude/skills/product-capability/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Product Capability skill for this task: A PRD, roadmap item, discussion, or founder note exists, but the implementation constraints are still implicit. Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# 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:

1. Product intent - issue, discussion, PRD, roadmap note, founder message 2. Current architecture - relevant repo docs, contracts, schemas, routes, existing workflows 3. Existing capability context - `PRODUCT.md`, design docs, RFCs, migration notes, operating-model docs 4. 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:

```text 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.

Intended uses

  • 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

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.