Product Requirements Document

Source: prd.md

22 lines

# Product Requirements Document
<!-- This defines WHAT to build and WHY — not HOW. Architecture comes later. -->

## Context

## Problem

## Users

## Requirements
<!-- Use: "The <system> shall <action>" for each requirement -->

### Functional Requirements

### Non-Functional Requirements

## Out of Scope
<!-- This section is mandatory — scope creep dies here -->

## Success Criteria

## Open Questions