replit-prd

# Replit PRD Generator

Create comprehensive Product Requirements Documents optimized for Replit Agent to build complex applications.

## When to Use

- Building complex applications with multiple features
- Need stakeholder alignment before development
- Want one-shot autonomous builds (entire app from single prompt)
- Require clear acceptance criteria and testing plans
- Working on team projects that need documentation

## PRD vs Simple Prompt

| Aspect | Simple Prompt | Full PRD |
|--------|---------------|----------|
| Features | 1-3 | 4+ |
| Pages/Screens | 1-3 | 4+ |
| User Roles | 1 | Multiple |
| Integrations | 0-1 | Multiple |
| Development Time | < 1 hour | Hours to days |
| Iterations Expected | Minimal | Multiple phases |

**Rule of thumb:** If you can describe it in 10 lines, use a prompt. If you need structure, use a PRD.

## PRD Template for Replit

```markdown
# [Product Name] - Product Requirements Document

## 1. Executive Summary

### Product Name
[Name]

### Version
1.0.0

### Last Updated
[Date]

### One-Line Description
[What it is and who it's for in one sentence]

### Problem Statement
[What problem does this solve? Why does it matter?]

### Success Metrics
- [Metric 1: e.g., "User can complete core task in under 2 minutes"]
- [Metric 2: e.g., "Zero critical bugs in core user flows"]
- [Metric 3: e.g., "Page load time under 3 seconds"]

---

## 2. User Personas

### Persona 1: [Name/Role]
- **Description:** [Who they are]
- **Goals:** [What they want to achieve]
- **Pain Points:** [What frustrates them currently]
- **Tech Comfort:** [Low/Medium/High]

### Persona 2: [Name/Role]
- **Description:** [Who they are]
- **Goals:** [What they want to achieve]
- **Pain Points:** [What frustrates them currently]
- **Tech Comfort:** [Low/Medium/High]

---

## 3. Technical Specifications

### Tech Stack
| Layer | Technology | Rationale |
|-------|------------|-----------|
| Frontend | [Framework] | [Why chosen] |
| Styling | [Library] | [Why chosen] |
|