# {Feature name}

## Problem Statement

The problem the user is facing, from the user's perspective.

## Solution

The solution to the problem, from the user's perspective.

## User Stories

A long, numbered list of user stories, each: "As an {actor}, I want {feature}, so that {benefit}." Cover all aspects of the feature. Prefer thin, end-to-end vertical slices over horizontal layers, and order them by dependency.

## Implementation Decisions

Modules built/modified, interfaces touched, technical clarifications, schema changes, API contracts, specific interactions. No file paths or code snippets (they go stale) — except a small snippet that encodes a decision more precisely than prose (a state machine, reducer, schema, or type shape), trimmed to the decision-rich part and noted as coming from a prototype.

## Testing Decisions

What makes a good test here (test external behaviour, not implementation details); which modules are tested; the seams the tests attach to (prefer existing, highest, fewest); prior art for similar tests in the codebase.

## Out of Scope

What this PRD deliberately does not cover.

## Notes

Anything else.
