prd-writer

name	prd-writer
description	Professional Product Requirements Document (PRD) writing for software products. Use when creating PRDs for MVPs, major releases, feature additions, demos/prototypes, urgent requirements, or architectural changes. Provides structured templates, priority frameworks (P0/P1/P2), user scenario patterns, acceptance criteria guidelines, and best practices for technical specifications.

PRD Writer

Write professional Product Requirements Documents following industry best practices and proven patterns.

Core Structure

Every PRD uses this 6-module structure:

1. Basic Specifications - Document metadata, version history
2. Document Overview - Background, scope, terminology
3. Product Description - Positioning, scenarios, workflows
4. Functional Requirements - Feature-by-feature detailed specs
5. Non-Functional Requirements - Performance, security, operations
6. Appendices - Milestones, tests, risks

Priority Framework

Assign every feature a priority:

• P0 (Must Have): Product fails without this. Hard blockers. Example: Core CRUD operations, critical integrations for AI products, urgent investor demo requirements
• P1 (Should Have): Significantly improves UX. Reasonable workarounds exist. Example: Advanced search, keyboard shortcuts, auto-save
• P2 (Nice to Have): Minor enhancements, low impact. Example: Custom themes, rare edge cases, social features Decision Rule: Ask "Can we ship without this?" If NO → P0. If "Yes but users will notice" → P1. If "Yes easily" → P2.

Writing Principles

1. Be Specific: Use quantifiable metrics ("API response <500ms" not "fast")
2. Show Examples: Every abstract concept needs 1+ concrete examples
3. User-Centric: Frame features as "As a [user], I want [goal], so that [benefit]"
4. Define Boundaries: Explicitly state what's IN scope (✅) and OUT scope (❌)
5. Testable Criteria: All acceptance criteria must be binary pass/fail

Feature Template

For each feature in Section 4, use this structure:

### 4.X Feature Module X: [Name] (P0/P1/P2)
 
#### 4.X.1 Feature Overview
[2-3 sentences: what it does, why it matters]
 
#### 4.X.2 User Scenarios
**Scenario A: [Title]**
1. User context: [Who and what they're doing]
2. User action: [What user does]
3. System response: [What system does]
4. User outcome: [What user sees]
 
#### 4.X.3 Priority
**[P0/P1/P2]**
Justification: [Why this priority]
 
#### 4.X.4 Pre-conditions
- [User state requirements]
- [System state requirements]
- [Dependencies]
 
#### 4.X.5 Detailed Requirements
 
##### UI/UX Specification
**Layout:** [ASCII mockup]
**Visual Style:** [Color table for Dark/Light modes]
**Interactions:** [Click, hover, keyboard behaviors]
 
##### Functional Logic
**Data Structures:**
```typescript
interface ModelName {
  field: type;  // Description
}

Algorithms: [Step-by-step processes] API Specs: [Endpoints with request/response examples]

4.X.6 Acceptance Criteria

Success Path:

• ✅ [Observable outcome 1]
• ✅ [Metric requirement] Failure Path:
• When [error], show [specific message] Edge Cases:
• [Maximum load behavior]
• [Empty state handling]

4.X.7 Additional Notes

Performance: [Specific targets] Dependencies: [Technical/feature dependencies] Future: [V2 considerations]

 
## Urgent Requirements
 
For time-critical features, add:
 
1. **Flag urgency in title**: "Feature X: Internationalization (P0 URGENT)"
2. **Explain context**: "Demo shipping to Chinese investors in 1 day, no time for video"
3. **Justify escalation**: Why P0 vs P1, what's blocked, impact if delayed
4. **Timeline breakdown**: Hour-by-hour allocation across 1-2 days
 
## Common Patterns
 
### Scenario Writing

User does X → System responds Y → User sees Z → Success state

 
### Acceptance Criteria

✅ When [condition], then [observable outcome] ✅ Response time <X for operation Y ✅ UI displays [element] in [state]

 
### Edge Cases to Document
- Empty states (no data)
- Maximum load (100+ items)
- Concurrent actions (race conditions)
- Network failures (timeout, offline)
- Validation failures (invalid input)
 
## Checklist
 
Before finalizing PRD:
 
- [ ] Every feature has P0/P1/P2 with justification
- [ ] User scenarios cover happy path + errors
- [ ] Acceptance criteria are testable (pass/fail)
- [ ] Edge cases documented for P0 features
- [ ] Visual mockups included (ASCII or diagrams)
- [ ] API specs complete with request/response
- [ ] Performance targets quantified
- [ ] Dependencies explicitly listed
- [ ] Scope boundaries defined (IN/OUT)
 
## Bundled Resources
 
For complete templates and detailed guidance:
 
- **references/prd_structure.md** - Full 6-module PRD template with section-by-section explanations
- **references/feature_template.md** - Comprehensive feature specification template with all subsections
- **references/examples.md** - Real-world PRD examples (MVP and urgent features)
- **references/best_practices.md** - Writing guidelines, pitfalls to avoid, stakeholder communication