03 prd
An AI-assisted product development pipeline for Claude Code. Go from a product idea to Figma screens in 8 structured steps, with specialized AI agents handling product management, design research, and visual construction.
npx -y skills add andrefabricio/prodotypor --skill 03-prdAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Step 3 of 8 — PRD creation. Produces Product Requirements Documents with user stories, acceptance criteria, and success metrics. Sub-commands: [continue] resume, [status] check progress, [update] force status refresh.
SKILL.md
4.6 KB, as published. Nobody here has run it
/03-prd — PRD Creation
Create Product Requirements Documents from the prioritized backlog.
Sub-command Router
Parse $ARGUMENTS:
- Contains
[status]→ Jump to Status Report section - Contains
[update]→ Jump to Force Status Update section - Contains
[continue]or empty → Jump to Execute section - Other text → Treat as specific feature/epic name to write PRD for
Prerequisites
Hard dependencies:
- Read
docs/workflow-status.md— verify step 02 status ==completed - Verify
docs/backlog/{{PROJECT_NAME}}-backlog.mdhas MVP scope locked (P0-P3 assigned)
If prerequisites fail:
- Report: "Step 03 cannot start. Missing: prioritized backlog with MVP scope."
- Suggest: "Run
/02-prioritizefirst." - Do NOT proceed.
Soft dependencies:
.impeccable.mdbrand direction (improves story quality but not blocking)
Execute
Phase 1: Determine Scope
- Read prioritized backlog — identify MVP features (P0 + critical P1)
- If
$ARGUMENTSnames a specific feature/epic, scope to that - If continuing, read existing PRDs in
docs/prds/to determine what's already written - List features that still need PRDs
Phase 2: Delegate to Product Manager Agent
For each feature/epic needing a PRD, spawn the product-manager agent:
Write a PRD for [feature name] in {{PROJECT_NAME}}.
Backlog entry: [relevant section from backlog] Template: [content of
templates/prd-template.md] User story template: [content oftemplates/user-story-template.md] Brand context: [from.impeccable.mdif available]Output requirements:
- Problem statement with user pain points
- ≥5 user stories in Given/When/Then format
- Acceptance criteria for each story
- Success metrics (adoption, engagement, retention, quality)
- Scope boundaries ("what we're NOT building")
- Dependencies and risks
- Save to
docs/prds/[feature-slug].md
Pipeline Context
Before delegating, read and summarize prior step outputs:
- Step 01-02 output: read MVP scope and priority assignments from backlog
- Include this summary in the agent prompt as "Pipeline Context"
Phase 3: Validate Output
- Verify at least 1 PRD file exists in
docs/prds/ - Check each PRD has: problem statement, ≥5 user stories, acceptance criteria, success metrics
- If validation passes → proceed to Phase 4
- If validation fails → proceed to Error Recovery
Error Recovery
If validation fails:
- Identify the specific failure (e.g., "only 3 user stories, need ≥5")
- Feed the error + partial output back to the agent:
"The PRD did not meet requirements: [specific failure]. Current output: [summary]. Please fix: [specific instruction]."
- Re-validate after the retry
- If retry also fails, mark step as
blocked (reason)indocs/workflow-status.md
Quality Gate (optional)
<!-- CUSTOMIZE: Define domain-specific quality checks for PRD output -->After structural validation, optionally assess quality:
- Read the PRD and check: Are user stories specific enough to derive screens? Do acceptance criteria have measurable outcomes?
- Score: pass / needs-revision
- If needs-revision, feed specific feedback to the agent (see Error Recovery)
Phase 4: Human Review Gate
- Update
docs/workflow-status.mdstep 03 status toneeds-review - Report PRD summary to the user
- Prompt: "Review the PRD(s). Run
/03-prd [continue]to approve, or provide feedback." - Only
[continue]afterneeds-reviewtransitions tocompleted
Phase 5: Report
Step 03 — PRD Creation: [status]
PRDs written: [count]
- [feature-name]: [story count] user stories
- [feature-name]: [story count] user stories
Total user stories: [count]
Next steps:
/04-inspiration — UI inspiration research (can run in parallel)
/05-design-doc — after inspiration research completes
Status Report
- Read
docs/workflow-status.md— extract step 03 section - List PRD files in
docs/prds/with story counts - Report completion percentage (PRDs written vs MVP features)
Force Status Update
- Glob
docs/prds/*.md— count PRDs - Read each, count user stories
- Compare against MVP feature list from backlog
- Update
docs/workflow-status.mdstep 03