product-requirements — Claude Code skill: PRD from a dialogue
Acts as a product owner, scores your requirements out of 100 and writes a PRD to docs/{feature-name}-prd.md.
npx skills add stellarlinkco/myclaude --skill product-requirements -a claude-codeWhat product-requirements does
This skill turns a vague feature idea into a requirements document. The agent introduces itself as Sarah, a product owner, reads README plus package.json or pyproject.toml to pick up the stack and conventions, then restates your request in that context and asks whether it got it right.
Next comes scoring out of 100: business value and goals (30 points), functional requirements (25), user experience (20), technical constraints (15), scope and priorities (10). Below 90, the skill asks clarifying questions through AskUserQuestion, two or three at a time, starting with the weakest category. Each answer triggers a rescore, so you see which area moved.
Once the threshold is met, it generates a PRD from a template: executive summary, problem statement, success metrics, personas, user stories with acceptance criteria, functional requirements with edge cases, technical constraints. The file lands in docs/{feature-name}-prd.md. One thing to plan for: the 90-point bar gates generation, so a fuzzy request means a longer interrogation instead of an instant document.
What it helps with
- turn a verbal feature pitch into a PRD
- spot gaps in requirements before coding starts
- define measurable success metrics
- break a feature into user stories with acceptance criteria
- write down what is out of scope for the release
Example prompts for the agent
- help me spec the CSV report export feature
- I need a PRD for the new profile settings page
- review my feature idea and tell me what is missing
How to install product-requirements
1Skills CLI (Vercel)
npx skills add stellarlinkco/myclaude --skill product-requirements -a claude-code2Manually: put the files in place
~/.claude/skills/product-requirements/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/product-requirements/
1Skills CLI (Vercel)
npx skills add stellarlinkco/myclaude --skill product-requirements -a codex2Manually: put the files in place
.agents/skills/product-requirements/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add stellarlinkco/myclaude --skill product-requirements -a cursor2Manually: put the files in place
.cursor/skills/product-requirements/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install stellarlinkco/myclaude product-requirements2Manually: put the files in place
.github/skills/product-requirements/SKILL.md1Skills CLI (Vercel)
npx skills add stellarlinkco/myclaude --skill product-requirements -a gemini-cli2Platform CLI
gemini skills install https://github.com/stellarlinkco/myclaude --path skills/product-requirementsManually: put the files in place
.devin/skills/product-requirements/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add stellarlinkco/myclaude --skill product-requirements -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about product-requirements
How do I install product-requirements in Claude?
Run npx skills add stellarlinkco/myclaude --skill product-requirements -a claude-code. The skill ends up at ~/.claude/skills/product-requirements/SKILL.md.
What does product-requirements do?
It runs an interactive requirements dialogue, scores the result out of 100, and at 90 or above generates a PRD in docs/{feature-name}-prd.md.
Why does the skill not write the PRD right away?
Generation starts only after the 90-point threshold. When requirements are thin, the skill asks clarifying questions via AskUserQuestion, two or three at a time.
