v0.dev PRD Generator (Simple Ver.)

Description

This prompt guides product leaders through a structured, v0.dev-optimized template to create a share-ready Product Requirements Document (PRD). It lays out clear sections for goals, user stories, functional specs, UX, metrics, and integrations while spotlighting code-generation snippets that match v0.dev’s conventions. Using it ensures consistent, high-quality PRDs that accelerate alignment and delivery.

As **Head of Product**, craft a production-ready **Product Requirements Document (PRD)** optimized for **v0.dev** code generation. Fill every section below using the project inputs provided, producing a document that can be directly shared with engineering and pasted into v0.dev.

---

## Project Inputs (fill these first)

| Input | Your Answer |
|---|---|
| **Project Name** | e.g., "SimpleTodo" |
| **One-line tl;dr** | e.g., "A minimal web app that lets users create, organise, and track personal tasks across devices." |
| **Top Business Goal** (+2-4 more) | e.g., "Ship MVP in four weeks and reach 30% seven-day retention within the first month." |
| **Top User Goal** (+2-4 more) | e.g., "Add a new task in under five seconds from any screen." |
| **Key Non-Goal** (+1-2 more) | e.g., "Real-time multiplayer collaboration is out of scope for the initial release." |
| **Main Personas & User Stories** | e.g., Busy Professional > "As a busy professional, I want keyboard shortcuts so I don't break focus." |
| **Must-have Features** (group > feature \| priority) | e.g., Core > TaskCreate \| P0 |
| **Tech Stack preferences** (if different from default) | e.g., "Use React 19 with TanStack Query." |
| **Top Success Metric** | e.g., "Average task-completion rate >= 60% within 24 hours." |
| **External Integrations** | e.g., "Google Calendar, Slack notifications" |

---

## PRD Output Structure

### 1. tl;dr
2-3 sentences covering: problem, solution, primary benefit, target user.

### 2. Goals

| Category | Goals (SMART format) |
|---|---|
| Business Goals | 3-5 measurable business outcomes |
| User Goals | 3-5 clear user benefits |
| Non-Goals | 2-3 explicitly out-of-scope items |

### 3. User Stories
Format each as: **Persona** > "As a [persona], I want [action], so that [benefit]."
Group by persona. Include at least 3 personas with 2-3 stories each.

### 4. Functional Requirements

| Group | Feature | Description | Priority |
|---|---|---|---|
| Core | e.g., TaskCreate | Short description | P0 |
| Core | e.g., TaskEdit | Short description | P0 |
| Enhancement | e.g., Filters | Short description | P1 |

### 5. User Experience
- **Entry & Onboarding:** First-time user flow (max 3 steps to value)
- **Core Flow:** Step-by-step with specific UI components (Tailwind + shadcn/ui)
- **Edge Cases:** Error states, empty states, loading states

### 6. v0.dev Prompt Library
Provide 3-5 copy-paste prompts for v0.dev, each targeting a specific UI component:
1. Prompt for the primary screen/dashboard
2. Prompt for the creation/input flow
3. Prompt for the settings/configuration view
4. (Optional) Prompt for mobile-responsive variant
5. (Optional) Prompt for dark mode variant

### 7. Narrative (200-300 characters)
Mini story: user pain > discovers solution > outcome achieved.

### 8. Success Metrics

| Category | Metric | Target |
|---|---|---|
| User | e.g., Task completion rate | >= 60% within 24h |
| Business | e.g., 7-day retention | >= 30% |
| Technical | e.g., p95 page load |  PR merge time |

Customize This Prompt