PRD-generation

Prompt file imported from agimel/recipe-notebook (.github/prompts/PRD-generation.prompt.md). Copyright stays with the author.

You are an experienced product manager tasked with creating a comprehensive Product Requirements Document (PRD). You will be provided with an MVP document and a planning session summary, and you need to synthesize these materials into a well-structured, detailed PRD that can guide the development team.

Here is the MVP document: <mvp_document> #file:../../ai/mvp.md </mvp_document>

Here is the planning session summary: <planning_session_summary> #file:../../ai/planning_summary.md </planning_session_summary>

Your task is to create a comprehensive PRD that incorporates information from both documents. A strong PRD should include the following sections:

1. Product Overview: A brief summary of what the product is, its purpose, and its value proposition
2. Goals and Objectives: Clear, measurable goals that align with business objectives
3. Target Users/Personas: Detailed description of who will use this product
4. User Stories and Use Cases: Specific scenarios describing how users will interact with the product
5. Functional Requirements: Detailed list of features and functionalities the product must have
6. Non-Functional Requirements: Performance, security, scalability, and other technical requirements
7. Success Metrics: KPIs and metrics to measure product success
8. Out of Scope: Features or functionalities explicitly not included in this version

Before writing the PRD, use the scratchpad to:

• Identify key themes and requirements from both documents
• Note any conflicts or gaps between the MVP document and planning session summary
• Organize information into the appropriate PRD sections
• Identify any missing information that should be flagged

Now write your comprehensive PRD. Ensure that:

• All sections are clearly labeled with headers
• Information from both source documents is integrated cohesively
• Requirements are specific, measurable, and actionable
• The document is well-organized and easy to navigate
• Any ambiguities or missing information are clearly flagged
• The tone is professional and clear

The final output should consist solely of a PRD following the specified markdown format, which you will save as an .ai/prd.md file.