Built here
Product requirements document
/product--prd
/product--prd is a Claude Code skill in the Business section. Turns a feature idea into a full PRD: problem, goals, scope, requirements, risks and success metrics.
Author's description
Write a full PRD from a feature idea — problem, goals, scope, success metrics
Use it when
- You have a feature idea and need a review-ready document
- You want to separate the validated problem from assumptions
- You need requirements a designer and an engineer can start from
Not for
- Replacing user research: a PRD on an unvalidated problem will be weak
- Detailed flows and edge cases: that is the feature spec
What you get
A prd_[feature].md file with TL;DR, problem, evidence, goals, metrics, Must/Should/Won't requirements, user flow, risks and milestones.
How to ask for it
/product--prd write the PRD for the new notifications feature/product--prd define the problem, scope, and success metrics for this idea/product--prd I need a full PRD to present to leadership
Install
curl -fsSL https://raw.githubusercontent.com/sgomez-dev/claude-skills/main/install.sh | bashAfter installing with the script, type /product--prd. Using Cursor, Windsurf or Codex? Platform guides
Questions about this skill
- What does it need from me before writing?
- The target user, evidence the problem exists, the business goal and any constraints. If they are missing, it asks before drafting.
- Does it invent baseline metrics?
- No. If there is no baseline it marks it "TBD — measure before build" rather than guessing.
- What if I give it a solution instead of a problem?
- It first reconstructs the underlying problem and confirms it with you.
Demo coming soon