Gated PRD generation — interrogates problem, user, and metric before drafting; refuses to draft on unknowns. Usage: /prd <feature-or-problem>
65
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Generate a concise, evidence-gated product requirements document for $ARGUMENTS.
/prd <feature-or-problem>$ARGUMENTS is the feature, initiative, or problem statement. If empty, ask for it before doing anything else.
Walk these one at a time. Do not batch them. Each answer feeds a required PRD section.
Refuse to draft the PRD if the answer to question 1 (problem), 2 (user), or 3 (metric) is unknown, circular, or "we'll figure it out later." Instead, output the open questions and the cheapest way to answer each (e.g., 5 customer interviews, a funnel query, a fake-door test). A PRD without a problem, a user, and a metric is a feature wish, not a requirements document.
Every PRD must contain all of these sections — emit the checklist at the end and mark each:
Keep it to ~2 pages. Use the repo template as the skeleton.
If the user has multiple candidate features, offer to RICE-score them before committing the PRD:
python3 product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20product-team/skills/product-manager-toolkit/SKILL.mdproduct-team/skills/product-manager-toolkit/assets/prd_template.mdproduct-team/skills/product-manager-toolkit/references/prd_templates.mdproduct-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py/code-to-prd — reverse-engineer a PRD from an existing codebase/rice — standalone RICE prioritizationalirezarezvani/claude-skills
27cfcd0
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.