Write a Product Requirements Doc Outline

Turn this idea into a PRD outline ready for engineering review:

Problem: [PROBLEM]
Who feels it: [USER / PERSONA]
Current workaround: [WORKAROUND]
Proposed solution: [SOLUTION]
Success metrics: [METRICS]
Constraints: [TECH, TIME, LEGAL]
Out of scope: [LIST]
Stakeholders: [NAMES / ROLES]

Requirements:
1. Structure as context, goals, non-goals, user stories, requirements, edge cases, launch plan.
2. Separate must-have vs nice-to-have clearly.
3. Include acceptance criteria written as testable statements.
4. Note open questions and owners.
5. Keep language concrete; avoid vague adjectives.

Deliverables:
1. A full PRD outline with ## sections (no top-level H1).
2. A one-paragraph executive summary.
3. A risk list with mitigation ideas.