03-prd — Claude Code skill: what it does, how to install
03-prd turns a need, idea or brainstorm into a structured product requirements document: a draft from a template, saved only once you approve it.
MIT ★ 571 updated 2026-10-29
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-pm@aidd-frameworkWhat 03-prd does
Two steps: a draft PRD against a template, then saving the version you approved. You feed it a feature description, a rough idea or a brainstorm; user stories can come along as raw material. The draft goes back and forth until you sign off.
The skill ships as a SKILL.md file holding two actions, draft and finalize, plus a set of ground rules. Product and lifecycle calls stay with you. Evidence, decisions and assumptions are kept apart, and source links and your earlier edits survive the rewrite.
Nothing is written without explicit approval, or a bounded authority passed in by the caller. No approval, no saved file. The document states what and why; a technical plan or user stories don't belong in it.
What it helps with
- draft a PRD from a rough idea instead of a blank template
- keep evidence, decisions and assumptions in separate sections
- carry source links and earlier edits into the final document
- reach an approved requirements doc before anything is written to disk
Example prompts for the agent
- Draft a PRD from this brainstorm and show me the draft before saving anything.
- Turn the notes in
idea.mdinto a product requirements document, save it only after I confirm. - Rework the assumptions section of the PRD draft, leave my edits and the source links alone.
How to install 03-prd
1Plugin marketplace
/plugin marketplace add ai-driven-dev/framework/plugin install aidd-pm@aidd-frameworkThis installs the whole aidd-pm plugin with all its skills
2Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 03-prd -a claude-code3Manually: put the files in place
~/.claude/skills/03-prd/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/03-prd/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 03-prd -a codex2Manually: put the files in place
.agents/skills/03-prd/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 03-prd -a cursor2Manually: put the files in place
.cursor/skills/03-prd/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework plugins/aidd-pm/skills/03-prd2Manually: put the files in place
.github/skills/03-prd/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 03-prd -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path plugins/aidd-pm/skills/03-prdManually: put the files in place
.devin/skills/03-prd/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 03-prd -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 03-prd
How do I install 03-prd in Claude Code?
Add the marketplace with /plugin marketplace add ai-driven-dev/framework, then run /plugin install aidd-pm@aidd-framework.
What does 03-prd do?
It builds a structured PRD from a need, idea or brainstorm: a template-based draft first, a saved file once you approve it.
Does 03-prd write user stories or a technical plan?
No. It stays on product requirements, and those are separate documents.
Source text
SKILL.md · MIT
--- name: 03-prd description: Generate a structured Product Requirements Document from a need, idea, or brainstorm, confirmed before save. Use when the user wants to draft or generate a PRD or product requirements. Not for user stories or a technical plan. argument-hint: need | brainstorm --- # PRD ```mermaid flowchart LR source([feature description, optionally with user stories]) --> draft --> finalize --> done([saved PRD]) ``` ## Actions Run the flow above. Read only the next action file. | Action | Does | | -------- | -------------------------------------- | | draft | draft per template, iterate to approval | | finalize | save the approved draft | ## Transversal rules - Keep product and lifecycle decisions with the user. - Separate evidence, decisions, and assumptions. - Preserve source links and existing edits. - Ask natural questions; never expose actions, references, or unchanged state. - Require explicit approval or caller-provided bounded authority before any write. - State what and why; never a technical plan or user stories.
© AI-Driven Dev · MIT · ai-driven-dev/framework