Product Capability

This is the PRD-to-SRS bridge you need when product intent is clear but implementation constraints are still fuzzy. It extracts the hidden assumptions senior engineers usually restate during review and turns them into a reusable capability contract: business rules, scope boundaries, invariants, data ownership, lifecycle transitions. You feed it a PRD or roadmap item, it gives you actors, states, interfaces, and a list of unresolved questions before code starts. Best used when a feature crosses multiple services and you need explicit constraints instead of vague planning prose. The output is durable enough to survive across sessions and harnesses.

skills.sh installs: 3.5K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill product-capability --agent claude-code

Installs into .claude/skills of the current project.

Files

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