New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Product Capability

by affaan-m in affaan-m/ECC

Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before…

MITAuto-check passedProduct & Project Management

Install Product Capability

skills CLI
$ npx skills add affaan-m/ECC --skill product-capability -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC product-capability --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/product-capability .claude/skills/product-capability && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
product-capability
GitHub stars
277k
Used in
2 other repos
Token cost
~1.1k tokens
SKILL.md length
474 words
Files
1
Skills in repo
683
Repo updated
First seen
Licence
MIT

At a glance

Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before…

  • Works in 4 steps: Restate the capability → Resolve capability constraints → Define the implementation-facing contract → …
  • The user needs an ECC-native PRD-to-SRS lane instead of vague planning prose
  • SKILL.md covers When to Use, Canonical Artifact, Non-Negotiable Rules and Inputs, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Product Capability is an agent skill from affaan-m/ECC. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • The user needs an ECC-native PRD-to-SRS lane instead of vague planning prose
  • Tasks that involve PRD writing

Example prompts

  • “/product-capability”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Restate the capability
  2. Resolve capability constraints
  3. Define the implementation-facing contract
  4. Translate into execution

What it can do on your machine

Read from SKILL.md and the folder at commit 2d515e4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Capability loads about 1.1k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 474 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit 2d515e4, republished under its MIT licence (© affaan-m). 474 words, ~1,109 tokens.

Download SKILL.mdSave it as .claude/skills/product-capability/SKILL.md (or your agent's skills folder).
name
product-capability
description
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.
metadata.origin
ECC

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

Show full SKILL.md (208 more words)Show less
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.

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/product-capability of affaan-m/ECC.

Open the folder on GitHubat commit 2d515e4

Used in 2 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Product Capability next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Capability compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Capability this skillaffaan-m/ECC277k2 repos~1.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Trellis Brainstormanjiemo/SunnyBeach1787 repos~4kAutomated safety check: PassApache-2.0
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT
Ralph Tui Create JSONsubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Trellis Brainstorm

    anjiemo/SunnyBeach

    Guides collaborative requirements discovery before implementation.

    178 GitHub starsUsed in 7 repos~4k tokens
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads Rust

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create JSON

    subsy/ralph-tui

    Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Prd Generator

    jamesrochabrun/skills

    Generate comprehensive Product Requirements Documents (PRDs) for product managers.

    216 GitHub starsUsed in 2 repos~3.8k tokens
    Product & Project ManagementAuto-check passed

More from affaan-m/ECC

All 682 skills in this repo

  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    277k GitHub starsUsed in 5 repos~3.1k tokens
    Auto-check passed

  • VideoDB Video Search and Editing

    affaan-m/ECC

    Ingests, indexes, searches, edits and monitors video, audio and live streams through the VideoDB Python SDK, returning stream links, clips and timestamps.

    277k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes

  • Docs Governance

    affaan-m/ECC

    Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references.

    277k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    277k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed

  • Master Agreement Generator

    affaan-m/ECC

    Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    277k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Frontend Design Direction

    affaan-m/ECC

    Set an ECC-specific frontend design direction for production UI work.

    277k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

Categories

Questions about Product Capability

What does Product Capability do?

Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before…. Product Capability is an agent skill from affaan-m/ECC. 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.

When should I use Product Capability?

Product Capability fits situations like: the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose; tasks that involve PRD writing.

How do I install Product Capability in Claude Code?

Run `npx skills add affaan-m/ECC --skill product-capability -a claude-code`. Or copy the skill folder (skills/product-capability in affaan-m/ECC) into .claude/skills/product-capability in your project. Claude Code loads it when a task matches its description.

How do I install Product Capability in Codex?

Run `npx skills add affaan-m/ECC --skill product-capability -a codex`. Or copy the skill folder (skills/product-capability in affaan-m/ECC) into .agents/skills/product-capability in your project. Codex loads it when a task matches its description.

Can I use Product Capability in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill product-capability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-capability, .gemini/skills/product-capability, .github/skills/product-capability and .opencode/skills/product-capability in your project.

What does Product Capability need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Capability is instructions for the agent only.

Does Product Capability access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Capability safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Capability use?

Product Capability is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Capability use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Product Capability?

Skills that share tags, products or a category with Product Capability: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Capability?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 276,673 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 11, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.