# PRD: [Feature or product name]

**Author:** [Name]  
**Status:** [Draft / In review / Approved]  
**Last updated:** [Date]

## 1. Overview
- **Problem Statement**: What problem are we solving? (2-3 sentences)
- **Proposed Solution**: High-level description of what we're building (2-3 sentences)
- **Success Metrics**: How we'll measure success (3-5 key metrics)

## 2. Context & Background
- **Why Now**: Why is this the right time?
- **Strategic Alignment**: How does this align with company objectives?
- **User Research Summary**: Key insights from research (if applicable)

## 3. User Stories & Use Cases
Format: "As a [user type], I want to [action] so that [benefit]"
- Include 3-7 primary user stories
- Add acceptance criteria for each

## 4. Requirements
**Functional Requirements:**
- Must-have features (P0)
- Should-have features (P1)
- Nice-to-have features (P2)

**Non-Functional Requirements:**
- Performance expectations
- Security considerations
- Accessibility requirements

## 5. Design & User Experience
- Link to design mocks or wireframes
- Key user flows
- Edge cases and error states

## 6. Technical Considerations
- Architecture implications
- Dependencies on other systems
- Technical risks and mitigations

## 7. Implementation Plan
- **Phase 1 (MVP)**: What goes in first version
- **Phase 2**: What comes next
- **Phase 3**: Future enhancements

## 8. Open Questions
- Decisions that still need to be made
- Stakeholders to consult
- Research needed

## 9. Appendix
- Research links
- Related documents
- Competitive analysis

---
From PM Claude Skills by Mohit Aggarwal (MIT licence): https://github.com/mohitagw15856/pm-claude-skills