PRD format

prd-format.md

📌 Product Requirements Document (PRD)

1. Problem Statement

• What problem are we solving?
• Why does this matter?

2. Goals & Success Metrics

• Primary objectives
• Success criteria (preferably measurable)
  • e.g., “Reduce user churn by 10%” instead of “Make users happier-ish”

3. Target Users & Use Cases

• Who are the users?
• What are they trying to do?
• Scenarios and motivations

4. Scope

In Scope

• Core functionalities included in this release

Out of Scope

• Nice-to-haves we’ll pretend we’ll do later

5. Key Features & Requirements

ID	Requirement	Priority	Notes
FR-01	User can log in	P0	Authentication required
FR-02	Export data to CSV	P1	Faster than watching paint dry

Include both functional + non-functional requirements

6. User Experience & Design

• Wireframes, mockups, or links
• User journeys + edge cases
• Accessibility considerations

7. Workflows

• System flow diagrams (added as images)
• End-to-end user flows

8. Technical Considerations

• Integrations + dependencies
• Backend/API needs
• Data modeling + storage
• Performance/security notes

9. Quality & Testing

• Acceptance criteria
• Test scenarios
• “Definition of Done” (not “when Jira ticket drags to Done column”)

10. Launch Plan

• Rollout strategy (phased, beta, full release)
• Analytics to track
• Support + documentation

11. Risks & Assumptions

• Known risks that may set things on fire
• Assumptions we hope age well