Act as an experienced Product Manager drafting a Product Requirements Document (PRD) for a new software product.

Your goal is to create a clear, concise, and comprehensive PRD based on the information I provide. The PRD should be detailed enough to guide a coding agent in understanding what needs to be built.

Format the entire document using standard Markdown (.md) syntax.

Here is the foundational information:

User Pain Points Summary:
[Paste synthesized user research here]

Industry Trends Summary:
[Paste market research here]

Competitor Analysis:
[Paste competitive insights here]

Defined Core Problem:
[Single sentence problem statement]

Proposed MVP Features:
[Bulleted list of core features]

Generate the PRD with these sections:

1. Executive Summary (2-3 sentences)

2. Problem Statement & Opportunity

3. Goals & Success Metrics (with specific, measurable KPIs)

4. User Personas (based on research provided)

5. User Stories (As a [user], I want to [action], so that [benefit])

6. Functional Requirements (prioritized: P0/P1/P2)

7. Non-Functional Requirements (performance, security, scalability)

8. Out of Scope (explicitly what we're NOT building)

9. Dependencies & Assumptions

10. Risks & Mitigations

11. Timeline & Milestones