# PRD Generation Prompt

## Context

You are creating a Product Requirements Document that synthesizes all discovery artifacts into a comprehensive spec.

## Input

- **Product slug:** `{slug}`
- **Read first (in order):**
  1. `agency/products/{slug}/discovery/brief.md`
  2. `agency/products/{slug}/discovery/competitors.md`
  3. `agency/products/{slug}/discovery/target-market.md`

## Instructions

1. Read all three artifacts thoroughly
2. Synthesize findings into a coherent PRD
3. Define clear MVP scope
4. Prioritize features based on persona pain points
5. Be specific about what's IN and OUT of scope

## Output Structure

Write to: `agency/products/{slug}/discovery/prd.md`

```markdown
# Product Requirements Document: {Product Name}

**Version:** 1.0
**Last Updated:** {Date}
**Status:** Draft — Pending Validation

---

## 1. Executive Summary

{3-4 sentence overview answering: What are we building? For whom? Why now?}

### Key Metrics

| Metric | Target | Timeframe |
|--------|--------|-----------|
| MVP Launch | Complete | {X} weeks |
| Beta Users | {X} | {Y} weeks |
| First Revenue | ${X} | {Y} weeks |

---

## 2. Problem Statement

### The Problem

{Detailed problem description from brief, enriched with persona insights}

### Impact

- **Frequency:** {How often users experience this}
- **Severity:** {Cost in time/money/frustration}
- **Current workarounds:** {What they do today}

### Evidence

- {Data point from research}
- {Quote from persona}
- {Market signal}

---

## 3. Target Users

### Primary User: {Persona Name}

{Summary from target-market.md}

**Key characteristics:**
- {Characteristic 1}
- {Characteristic 2}

**Primary pain point:** {The #1 problem we solve for them}

### Secondary User: {Persona Name}

{Brief summary}

### Non-Users (Explicitly Out of Scope for v1)

- {User type we're NOT targeting and why}
- {User type we're NOT targeting and why}

---

## 4. Competitive Landscape

### Key Competitors

| Competitor | Positioning | Our Advantage |
|------------|-------------|---------------|
| {Name} | {Their angle} | {How we're different} |
| {Name} | {Their angle} | {How we're different} |

### Our Positioning

{2-3 sentences on how we position against competitors — from competitors.md}

---

## 5. Solution Overview

### Product Vision

{One sentence describing the ideal future state}

### Core Value Proposition

{The primary benefit in user terms}

### Key Capabilities

1. **{Capability 1}** — {What it enables}
2. **{Capability 2}** — {What it enables}
3. **{Capability 3}** — {What it enables}

---

## 6. MVP Features

### P0 — Must Have (Launch Blockers)

These features are required for MVP launch.

#### F-001: {Feature Name}

**Description:** {What it does}
**User value:** {Why users need it}
**Acceptance criteria:**
- [ ] {Criterion 1}
- [ ] {Criterion 2}
- [ ] {Criterion 3}

**Complexity:** {Low/Medium/High}
**Dependencies:** {None or list}

---

#### F-002: {Feature Name}

{... same structure ...}

---

#### F-003: {Feature Name}

{... same structure ...}

---

### P1 — Should Have (Post-MVP)

Features to add in first iteration after MVP.

#### F-010: {Feature Name}

**Description:** {What it does}
**User value:** {Why users want it}
**Target release:** v1.1

---

### P2 — Nice to Have (Future)

#### F-020: {Feature Name}

**Description:** {What it does}
**Rationale for deferral:** {Why it can wait}

---

## 7. Non-Goals (Explicitly Out of Scope)

These are things we are **intentionally NOT building** in v1:

1. **{Non-goal 1}** — {Why we're excluding it}
2. **{Non-goal 2}** — {Why we're excluding it}
3. **{Non-goal 3}** — {Why we're excluding it}

---

## 8. Technical Considerations

### Platform

- **Web app:** {Yes/No, details}
- **Mobile:** {Yes/No, details}
- **API:** {Yes/No, details}

### Integrations

- {Integration 1} — {Why needed}
- {Integration 2} — {Why needed}

### Data & Privacy

- {Data we'll collect}
- {Privacy considerations}
- {Compliance requirements if any}

### Performance Requirements

- {Load time targets}
- {Concurrent user expectations}

---

## 9. Success Metrics

### North Star Metric

**{Metric name}:** {Definition}
**Target:** {Value} by {Date}

### Supporting Metrics

| Category | Metric | Target | How We'll Measure |
|----------|--------|--------|-------------------|
| Acquisition | {Metric} | {Target} | {Method} |
| Activation | {Metric} | {Target} | {Method} |
| Retention | {Metric} | {Target} | {Method} |
| Revenue | {Metric} | {Target} | {Method} |

---

## 10. Open Questions

### Must Answer Before Build

1. **{Question}** — {Why it matters}
2. **{Question}** — {Why it matters}

### Can Answer During Build

1. **{Question}** — {Proposed approach to learn}

---

## 11. Timeline & Milestones

| Milestone | Description | Target Date |
|-----------|-------------|-------------|
| Design Complete | UI/UX approved | Week {X} |
| MVP Dev Complete | All P0 features | Week {X} |
| Internal Testing | Bug fixes | Week {X} |
| Beta Launch | First users | Week {X} |
| Public Launch | GA release | Week {X} |

---

## 12. Risks & Mitigations

| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| {Risk 1} | {H/M/L} | {H/M/L} | {How we'll address} |
| {Risk 2} | {H/M/L} | {H/M/L} | {How we'll address} |

---

## Appendix

### A. Glossary

- **{Term}:** {Definition}

### B. References

- Brief: `discovery/brief.md`
- Competitors: `discovery/competitors.md`
- Target Market: `discovery/target-market.md`
```

## Quality Checklist

Before saving, verify:
- [ ] Executive summary is crisp and clear
- [ ] Features are specific with acceptance criteria
- [ ] Non-goals are explicit
- [ ] Metrics are measurable
- [ ] Synthesizes insights from all previous artifacts

## After Completion

1. Update progress.md: `[timestamp] ✓ Step 4/5: PRD generated with X P0 features`
2. Update workflow.json: `progress: 80`
