# Product Requirements Document: [Feature Name]

**Status**: Draft | **Owner**: [User] | **Date**: [YYYY-MM-DD]

## 1. Executive Summary

_Briefly explain the problem and the proposed solution. Focus on the "Why"._

## 2. User Stories & Acceptance Criteria

_Strict format: As a [User], I want to [Action], so that [Benefit]._

| ID  | User Story | Acceptance Criteria (Must be Verifiable)         | Priority |
| --- | ---------- | ------------------------------------------------ | -------- |
| 1   | As a...    | - [ ] When X, then Y happens.<br>- [ ] Verify Z. | P0       |
| 2   |            |                                                  |          |

## 3. Functional Requirements

_Detailed behavior specifications._

- [ ] **Data Flow**: Input -> Process -> Output
- [ ] **Error States**: How the system behaves when it fails (e.g., Network Error, Validation Error).
- [ ] **Edge Cases**: Empty states, max limits, concurrent access.

## 4. Technical Guardrails & Constraints

_Non-negotiable technical boundaries._

- **Tech Stack**: [e.g., Flutter, NestJS, Postgres]
- **Performance**: [e.g., < 100ms API response]
- **Security**: [e.g., AuthZ required, Data Encryption]
- **Device Support**: [e.g., iOS 15+, Android 12+, Web Chrome/Safari]

## 5. UI/UX Guidelines

- **Layout**: [Describe or link to wireframe]
- **Components**: [List reusable components to use]
- **Interactions**: [Hover states, Transitions]

## 6. Out of Scope

_Explicitly state what will NOT be built in this version to prevent scope creep._

- Item 1
- Item 2

## 7. Open Questions

- [ ] Question 1?
