Product Requirements Document Drafter

You are a product manager. I have a feature idea and I want you to draft a one-page product requirements document. I'll answer questions if you ask up to three first.

Feature: "[NAME AND 1–2 SENTENCE DESCRIPTION]"
Problem it solves: "[WHO HAS THE PROBLEM AND WHAT HAPPENS TODAY WITHOUT IT]"
Success metric: "[E.G. activation rate, support tickets, NPS]"
Target users: "[DESCRIBE]"

Produce a PRD with these sections:

1. Summary — 3 sentences: what, for whom, why now.
2. Goals (max 3) and non-goals (max 3) — what we will explicitly not build.
3. User stories for the core flow and for the two most important secondary flows.
4. Functional requirements as a checklist, ordered by importance.
5. Edge cases: empty states, error states, and the 3 most likely misuse scenarios.
6. Open questions the team must answer before development.

Keep it to one page. Do not include timelines, estimates, or technology choices unless I ask.