/prd-generator

name: prd-generator
description: Generates comprehensive Product Requirements Document from product plan. Creates PRD.md with features, user stories, acceptance criteria, and success metrics. Use when creating product requirements.
allowed-tools: [Read, Write, Glob, Grep, AskUserQuestion]
last_verified: 2026-07-16
review_by: 2027-06-22
os_version: iOS 27 / macOS 27

PRD Generator Skill

Generate comprehensive Product Requirements Document from product development plan.

Metadata

• **Name**: prd-generator
• **Version**: 1.0.0
• **Role**: Product Manager
• **Author**: ProductAgent Team

When This Skill Activates

This skill activates when the user says:

• "generate PRD"
• "create product requirements"
• "write product requirements document"
• "generate requirements doc"
• "create PRD from plan"

Description

You are a Product Manager AI agent specializing in iOS/macOS app requirements. Your job is to transform a product development plan (generated by the product-agent skill) into a comprehensive, actionable Product Requirements Document (PRD).

Prerequisites

Before activating this skill, ensure: 1. A product development plan exists (from the product-agent skill output) 2. The plan includes: problem analysis, MVP scope, positioning, and target audience 3. User has reviewed and approved the product development plan

Input Sources

Read and extract information from:

1. **Product development plan markdown file** (typically saved as `product-plan-*.md`)

• Problem statement and analysis
• Target users and pain points
• MVP scope and core features
• Positioning and value proposition
• Success criteria

2. **Competitive Analysis** (optional, if exists - from `competitive-analysis` skill) Look for: `competitive-analysis.md`, `docs/competitive-analysis.md`, or embedded in product plan

• Competitor list with strengths/weaknesses
• Feature matrix and gaps
• Pricing analysis
• Differentiation opportunities
• Market positioning map

**Integration**: Use competitive insights to:

• Inform feature priorities (fill gaps competitors miss)
• Validate positioning (differentiation)
• Set pricing context
• Identify unique value propositions

3. **Market Research** (optional, if exists - from `market-research` skill) Look for: `market-research.md`, `docs/market-research.md`, or embedded in product plan

• TAM/SAM/SOM market sizing
• Market growth trends
• Entry barriers
• Distribution channels
• Revenue potential

**Integration**: Use market research to:

• Validate opportunity size
• Inform success metrics (realistic targets based on market)
• Identify risks (entry barriers)
• Set revenue expectations

4. **User clarifications** (ask if needed):

• Additional feature requirements
• Specific user flows to prioritize
• Timeline constraints
• Platform-specific considerations

Output

Generate `docs/PRD.md` with the following structure:

# Product Requirements Document: [App Name]

**Version**: 1.0.0
**Last Updated**: [Date]
**Status**: Draft / In Review / Approved
**Owner**: Product Manager
**Platform**: iOS / macOS

---

## 1. Product Overview

### 1.1 Vision Statement
[One-paragraph vision for the product - what it aspires to achieve]

### 1.2 Target Audience
**Primary**: [Detailed description of primary users]
**Secondary**: [Secondary audience if applicable]

### 1.3 Success Metrics
- [Metric 1]: [Target value]
- [Metric 2]: [Target value]
- [Metric 3]: [Target value]

---

## 2. User Personas

### 2.1 Primary Persona: [Persona Name]

**Demographics**:
- Age: [Range]
- Occupation: [Description]
- Tech savviness: [Low/Medium/High]
- Location: [Geographic focus]

**Pain Points**:
1. [Pain point 1 - be specific]
2. [Pain point 2]
3. [Pain point 3]

**Goals**:
1. [Goal 1 - what they want to achieve]
2. [Goal 2]
3. [Goal 3]

**Typical Day**:
[Brief narrative of how this persona currently addresses the problem]

**Quote**: "[A quote that captures their frustration or need]"

### 2.2 User Journey Map

**Current State** (Before using the app):
1. [Step 1 of current workflow]
2. [Step 2 - highlight pain points]
3. [Step 3]
4. [Pain point or frustration]

**Future State** (With the app):
1. [Step 1 - how the app improves it]
2. [Step 2 - benefits]
3. [Step 3 - outcomes]

---

## 3. Features & Requirements

### 3.1 Core Features (MVP - Must Have)

#### Feature 1: [Feature Name]

**Priority**: P0 (Critical)
**Complexity**: Low / Medium / High
**Estimated Effort**: [X] weeks

**User Story**:
As a [user type], I want [action], so that [benefit].

**Acceptance Criteria**:
```gherkin
Given [precondition]
When [action]
Then [expected result]

Given [precondition 2]
When [action 2]
Then [expected result 2]

**Description**: [Detailed description of what this feature does and why it's needed]

**Dependencies**:

• [Dependency 1]
• [Dependency 2]

**Success Metrics**:

• [Metric 1]: [How to measure success]
• [Metric 2]: [Target value]

**Edge Cases**:

• [Edge case 1 and how to handle]
• [Edge case 2]

---

Feature 2: [Feature Name]

[Repeat structure for each MVP feature]

---

3.2 Deferred Features (Post-MVP - Phase 2)

**Feature**: [Deferred Feature Name] **Rationale for Deferral**: [Why this is not in MVP] **Planned for**: Version 1.1 / Phase 2

[List all deferred features with brief descriptions]

---

4. User Flows

4.1 Onboarding Flow

**Goal**: Help new user understand value and start using core feature

**Steps**: 1. **Launch Screen**

• Show: Value proposition and hero image
• Actions: [Sign Up] [Sign In] [Skip]

2. **Registration** (if user chooses Sign Up)

• Required: [Email, Name, ...]
• Optional: [Profile photo, ...]
• Validation: [Email format, password strength]

3. **Welcome Tutorial** (optional, skippable)

• Screen 1: [Key feature highlight]
• Screen 2: [How to use core functionality]
• Screen 3: [Call to action]

4. **First Task**

• Guide