prd-templates

# PRD Templates

Comprehensive PRD (Product Requirements Document) templates and frameworks for documenting product requirements and driving successful execution.

## When to Use This Skill

**Auto-loaded by agents**:
- `requirements-engineer` - For Amazon PR/FAQ, comprehensive PRD, and lean PRD templates

**Use when you need**:
- Writing product requirements documents
- Documenting feature specifications
- Aligning cross-functional teams
- Communicating product decisions
- Creating feature briefs
- Defining project scope
- Establishing success metrics

## What is a PRD?

A PRD is the primary document for defining what to build and why. It serves as:
- **Alignment tool**: Gets everyone on the same page
- **Decision artifact**: Documents what and why
- **Communication vehicle**: Shares vision across teams
- **Execution blueprint**: Guides building and launch
- **Historical record**: Captures rationale for future decisions

**A great PRD answers**:
- What are we building?
- Why are we building it?
- Who is it for?
- How will we know it's successful?
- What are we explicitly NOT building?

---

## When to Use Which Template

We provide 4 ready-to-use PRD templates for different contexts:

### Lean PRD
**Use for**: Small features, enhancements, bug fixes
**Effort**: 1-2 hours to write
**Length**: 1-2 pages
**Audience**: Engineering team

**Best for**:
- Features requiring < 1 week of development
- Well-understood problems with clear solutions
- Internal tools or quick experiments
- Low cross-functional complexity

**Template**: `assets/lean-prd-template.md`

---

### Comprehensive PRD (Standard)
**Use for**: Most features, new capabilities, significant enhancements
**Effort**: 4-8 hours to write
**Length**: 3-5 pages
**Audience**: Cross-functional team

**Best for**:
- Standard features (1-4 weeks of development)
- Customer-facing changes
- Features requiring cross-functional coordination
- New capabilities or platform features

**Template**: `assets/comprehensive-prd-t