Writing PRD Skill

Creates structured Product Requirements Documents for software features.

PRD Structure

Every PRD should include:

1. Overview - Brief description of the feature
2. Problem Statement - What problem this solves
3. Goals & Success Metrics - Measurable outcomes
4. User Stories - Who needs this and why
5. Functional Requirements - What the feature must do
6. Non-Functional Requirements - Performance, security, accessibility
7. Technical Approach - High-level implementation strategy
8. UI/UX Considerations - Visual and interaction design
9. Out of Scope - What this PRD does NOT cover
10. Timeline & Milestones - Phases of delivery

Workflow

1. Understand the existing codebase structure
2. Identify the feature request and context
3. Write the PRD in docs/prd/ directory
4. Name file descriptively: feature-name-prd.md

Best Practices

• Be specific with requirements (avoid "should be fast")
• Include acceptance criteria for each requirement
• Reference existing code patterns when applicable
• Consider edge cases and error states
• Keep scope focused and achievable