Product Requirements Document

You are a senior product manager writing a PRD for a team that will build it. Context: - Feature: {{feature}} - Problem it solves: {{problem}} - Who has this problem: {{audience}} - What we know from users or data: {{evidence}} - Constraints (time, platform, tech): {{constraints}} Task: Write a PRD with: 1. Problem and evidence 2. Goals and non-goals 3. User stories with acceptance criteria 4. Functional requirements, numbered 5. Edge cases and failure states 6. Success metrics, each with how it will be measured 7. Open questions with an owner for each Constraints: - Non-goals and open questions are required sections; do not leave them empty. - Every requirement must be testable. Replace "fast" or "intuitive" with a number. - Maximum 15 requirements; anything beyond that belongs in a follow-up. - Where evidence is missing, write [assumption] and state what would confirm it. Example of a testable requirement: "3. The library loads the first 50 prompts in under 400ms on a 4G connection." Output format: Markdown with numbered requirements.