PRD Generator

# Task
Draft a PRD that product, design, and engineering can align on.

# Inputs
- Product or feature: {product_or_feature}
- Problem: {problem}
- Target users: {target_users}
- Goal: {goal}
- Scope: {scope}
- Constraints: {constraints}

# Pre-flight
If scope or users are vague, ask up to 3 clarifying questions AND draft with stated assumptions.

# PRD structure
1. **Executive summary** (3-5 sentences): What we're building, for whom, and why now.
2. **Problem statement**: The user problem in their words. Include evidence if provided.
3. **Goals and success metrics**: 2-3 measurable outcomes. Use this format:
   - Goal: [what we want]
   - Metric: [how we measure]
   - Target: [specific number or threshold]
4. **Target users**: Who benefits, who doesn't. Be specific about segment boundaries.
5. **User stories** (5-8): As a [role], I want [action], so that [outcome]. Prioritize each:
   - P0: Must have for launch
   - P1: Should have, important
   - P2: Nice to have, can defer
6. **Scope**: What's IN and what's explicitly OUT. Use two columns.
7. **Requirements**: Functional requirements as a numbered list. Each testable and unambiguous.
8. **Non-functional requirements**: Performance, security, accessibility constraints.
9. **Risks and open questions**: What could go wrong or needs more research.
10. **Assumptions**: What we're assuming is true. Mark each [TO VALIDATE].

# Rules
- Write requirements as testable statements ("User can X" not "System should support X").
- Every P0 user story must have corresponding requirements.
- Flag any requirements that conflict with stated constraints.

# Output
Return the complete PRD using all 10 sections.

<context>
  <product_or_feature>{product_or_feature}</product_or_feature>
  <problem>{problem}</problem>
  <target_users>{target_users}</target_users>
  <goal>{goal}</goal>
  <scope>{scope}</scope>
  <constraints>{constraints}</constraints>
</context>
<task>Draft a PRD that product, design, and engineering can align on.</task>
<instructions>
  If scope or users are vague, ask up to 3 questions AND draft with assumptions.

  Structure: executive summary, problem statement, goals with metrics and targets, target users, user stories (5-8 with P0/P1/P2 priority), scope (IN/OUT), functional requirements (testable), non-functional requirements, risks, assumptions [TO VALIDATE].

  Every P0 story must have requirements. Flag conflicts with constraints.
</instructions>
<output>
  Return the complete PRD with all 10 sections.
</output>

Product or feature: {product_or_feature}
Problem: {problem}
Target users: {target_users}
Goal: {goal}
Scope: {scope}
Constraints: {constraints}

If vague, ask up to 3 questions AND draft with assumptions.

Structure: executive summary, problem, goals (with metrics/targets), users, user stories (5-8, P0/P1/P2), scope IN/OUT, functional requirements (testable), non-functional requirements, risks, assumptions [TO VALIDATE].

Based on the entire content above, return the complete PRD.