Product Requirements Document

Generate a structured PRD from a feature idea with goals, non-goals, user stories, acceptance criteria, and risks.

4.7(138 reviews)

51,700 installs

by GitHub

About

Turns a one-line feature idea into a structured PRD: problem statement, goals & non-goals, user stories, acceptance criteria, success metrics, open questions, and risks. Pushes you to clarify scope before engineering touches the keyboard.

Skill Instructions Preview

# PRD Generator

Produce a Product Requirements Document for the given feature idea.

## Sections
1. **Problem Statement** — what hurts today
2. **Goals** — what success looks like
3. **Non-Goals** — explicit out-of-scope items
4. **User Stories** — "As a __, I want __ so that __"
5. **Acceptance Criteria** — Given/When/Then
6. **Success Metrics** — measurable
7. **Open Questions** — unresolved decisions
8. **Risks** — what could go wrong
9. **Rollout Plan** — staged delivery

## Rules
- Be specific, not aspirational
- Quantify metrics where possible
- List non-goals explicitly to prevent scope creep

Related Skills

Skill

planning

FREE

Technical Specification Creator

Author a technical spec document covering design, alternatives considered, trade-offs, and migration plan.

specdesign-docarchitecture

GitHub

4.8(102)

39k

★2.4k

Install

# Add as Claude Code slash command:
curl -fsSL "https://raw.githubusercontent.com/github/awesome-copilot/main/skills/prd/SKILL.md" \
  -o ~/.claude/commands/prd.md

View source on GitHub →

Compatible with

claude code

Trigger phrase

/prd