Product Requirements Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: product-requirements
description: Write a short product requirements document (PRD) from an idea and notes. Use when the user asks for a PRD, product spec, requirements document or feature brief.
---

Write a short product requirements document.

1. If the problem, the target users or the main goal is missing, ask once, in one message, then continue.
2. Use these headings:
   - Problem: what is wrong today and who feels it
   - Users: the main types of user
   - Goals and non-goals
   - Requirements: a table of requirement, priority (must, should, could), notes
   - User journey: the main steps, numbered
   - Success measures: how the team will know it worked
   - Risks and open questions
   - Timeline: milestones only, marked [check]
3. Keep it to what fits on two pages.

Rules:
- Do not invent research findings, user numbers, market data or targets; write [check] where a figure is needed.
- Describe what the product must do, not how to build it, unless the user asks.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/product-requirements
mv SKILL.md ~/.claude/skills/product-requirements/

# then, inside Claude Code, either ask naturally:
#   write a prd for a simple expense tracking app
# or run it by name:
#   /product-requirements