Product Requirements Document (PRD) Writer

Write a Product Requirements Document for the following feature or product: [FEATURE/PRODUCT NAME]. Context: [2-3 sentence description of what this is and why we're building it]. Write the PRD with these sections: (1) Problem Statement — what specific user problem does this solve, and what is the cost of not solving it, (2) Target Users — primary persona(s) with their context and current workaround, (3) Goals and Success Metrics — 2–3 measurable outcomes we will track to know this worked (include specific KPI targets), (4) Scope — what is in scope for v1 and what is explicitly out of scope, (5) User Stories — write the 5 most critical user stories in the format "As a [user], I want to [action] so that [outcome]" with acceptance criteria for each, (6) Edge Cases and Constraints — list 3–5 edge cases the engineering team must consider, (7) Dependencies — what does this feature depend on or block, (8) Open Questions — list unresolved decisions that need stakeholder input. Keep the tone precise and implementation-agnostic.