# PRD Template Structure
Use this structure when generating PRDs.
## 1. Introduction/Overview
Briefly describe the feature and the problem it solves. State the goal in 2-3 sentences.
## 2. Goals
List specific, measurable objectives:
- Goal 1
- Goal 2
- Goal 3
## 3. User Stories
Format: "As a [user type], I want to [action] so that [benefit]."
Include 3-5 user stories covering primary use cases.
## 4. Functional Requirements
Number each requirement. Use clear, testable language.
1. The system must allow users to [action].
2. The system must display [information] when [condition].
3. The system must validate [input] before [action].
## 5. Non-Goals (Out of Scope)
Explicitly state what this feature will NOT include:
- Not included: [feature/functionality]
- Not included: [feature/functionality]
## 6. Design Considerations (Optional)
Include if relevant:
- UI/UX requirements
- Link to mockups
- Relevant components/styles
## 7. Technical Considerations (Optional)
Include if relevant:
- Known constraints
- Dependencies
- Integration points (e.g., "Should integrate with existing Auth module")
## 8. Success Metrics
How will success be measured?
- Metric 1: [e.g., "Reduce support tickets related to X by 20%"]
- Metric 2: [e.g., "Increase user engagement by 10%"]
## 9. Open Questions
List remaining questions or areas needing clarification:
- [ ] Question 1
- [ ] Question 2
