
Create a Product Requirements Document
Write a lean, decision-ready product requirements document (PRD) for a feature or product.
- Repository
- phuryn/pm-skills
- Stars
- 27,616
- Licence
- MIT
- Files
- 1 file
What it does
Once installed, the agent writes a short product requirements document, the kind a product manager circulates so engineers, designers and leadership agree on what to build first and why. It follows an 8-section template covering the summary, background, goals, target user groups, a structured value proposition, the solution, and the release plan. It asks you for missing key facts before writing, researches the market when useful, and marks anything it could not confirm as an assumption rather than presenting it as fact.
Great for
- Product managers writing a first PRD or feature spec
- Founders or team leads who need to align a small team on a new feature
- Anyone reviewing an existing PRD to find gaps and cuts
Skip it if
- Final legal, financial or compliance requirements, because the skill gives product-planning guidance and does not check facts against authoritative sources
- Teams that already use a different required PRD format, since the output follows this template
Try asking
- “Write a lean PRD for a new onboarding flow for our note-taking app”
- “Review this existing feature spec and tell me what is missing or can be cut”
- “Draft a product requirements document for a subscription reminder feature”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
create-prd.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip create-prd.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip create-prd.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Give the agent your evidence of the problem, your target users and how you will measure success before asking for a PRD, since it will ask for these first.
- Ask for the detailed version only when the lean one is not enough; the default is about one to two pages.
- Check the assumptions and open questions section, and validate those points with real users before building.
What's inside
- SKILL.md
Redistributed unmodified from phuryn/pm-skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.