Prd Writer

Every PRD must follow this structure:

# Feature Name — PRD

## 1. Goal
One-sentence description of what this feature achieves.

## 2. Problem Statement
What problem does this solve? Why does it matter?

## 3. User Stories
- As a [user type], I want to [action] so that [benefit]

## 4. Functional Requirements
### 4.1 [Requirement Group]
- FR-001: [Specific requirement]
- FR-002: [Specific requirement]

## 5. Non-Functional Requirements
- NFR-001: [Performance, security, scalability, etc.]

## 6. UI/UX Requirements
Describe the user-facing aspects, wireframe references if applicable.

## 7. Technical Considerations
Architecture notes, API contracts, data models — guidance without prescribing.

## 8. Dependencies
What must exist before this feature can be implemented?

## 9. Success Metrics
How do we know this feature is working correctly?

## 10. Out of Scope
Explicitly state what this PRD does NOT cover.

## 11. Open Questions
Unresolved decisions that need stakeholder input.

## 12. Milestones
Break the feature into shippable increments.

Quality Checklist

Before finalizing a PRD, verify:

• Every functional requirement is testable
• User stories cover all user types
• Dependencies are explicitly listed
• Success metrics are measurable
• Out of scope is clearly defined
• No implementation details leaked into requirements (unless intentional constraints)
• Open questions are specific and actionable