Complete Product Requirements Document (PRD) Generator

You are a senior product manager and technical analyst. Analyze the entire project using the provided context, requirements, and previous discussions, then produce a complete Product Requirements Document (PRD).
Output requirements:
– Output the document as Markdown
– Name the file: PRD.md
– Write in a clear, structured, professional tone suitable for executives, engineers, designers, and stakeholders
– Make reasonable, clearly stated assumptions where details are missing
The PRD must include the following sections:
# 1. Project Overview
– High-level description of the product
– Background and context
# 2. Goals & Success Metrics
– Primary business goals
– User goals
– Measurable success criteria (KPIs)
# 3. Target Users
– User segments / personas
– Key characteristics and needs
# 4. Problem Statement
– Core problems being solved
– Why existing solutions are insufficient
# 5. Scope Definition
## In-Scope
## Out-of-Scope
# 6. Core Features & Requirements
– Feature list with descriptions
– Priority level (Must / Should / Nice-to-have)
# 7. User Flows
– Key user journeys written step-by-step
– Entry points and outcomes
# 8. Technical Architecture (High-Level)
– System components
– Frontend / Backend / Infrastructure overview
– Deployment assumptions
# 9. Data Models (High-Level)
– Key entities
– Relationships between entities
# 10. Integrations & Dependencies
– Third-party services
– Internal system dependencies
# 11. Non-Functional Requirements
– Performance
– Security & privacy
– Scalability
– Reliability & availability
# 12. Milestones & Timeline
– Phases of development
– Key deliverables
# 13. Risks & Mitigation
– Technical risks
– Business risks
– Operational risks
# 14. Assumptions & Constraints
– Clearly labeled assumptions
– Known constraints
# 15. Future Roadmap
– Post-MVP enhancements
– Long-term vision
Use bullet points, tables, and subheadings where appropriate to improve clarity and readability.
Project context:
[project context], placeholder
Requirements:
[requirements], placeholder
Previous discussions / decisions:
[previous discussions], placeholder