# Create Prd

> Create a comprehensive Product Requirements Document (PRD) for a new app or feature. Use when starting a new project or major feature.

- Skill: `duboc/create-prd` (Agent Skill)
- Install (CLI): `npx skillmds@latest add duboc/create-prd`
- Raw SKILL.md: https://api.skillmd.com/api/skills/duboc/create-prd/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: duboc (https://skillmd.com/u/duboc)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/duboc/create-prd

---


# Create Product Requirements Document

Create a comprehensive PRD following best practices.

## PRD Structure

### Template: `docs/PRD.md`

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

## Executive Summary
[2-3 sentences describing the product/feature and its value proposition]

## Problem Statement
### Current Situation
[Describe the current state and pain points]

### Desired Outcome
[Describe the ideal end state]

## Target Users
### Primary User Persona
- **Name**: [Persona name]
- **Role**: [Role/occupation]
- **Goals**: [Key goals]
- **Pain Points**: [Current frustrations]

### Secondary User Personas
[Additional personas if applicable]

## Success Metrics
| Metric | Target | Measurement Method |
|--------|--------|-------------------|
| [Metric 1] | [Target] | [How to measure] |
| [Metric 2] | [Target] | [How to measure] |

## Core Features

### Feature 1: [Feature Name]
**Priority**: P0/P1/P2
**User Story**: As a [user], I want to [action] so that [benefit]

**Acceptance Criteria**:
- [ ] Criterion 1
- [ ] Criterion 2

### Feature 2: [Feature Name]
[Repeat structure]

## Non-Functional Requirements

### Performance
- App launch time: < 2 seconds
- API response handling: < 500ms perceived
- Smooth scrolling: 60fps

### Accessibility
- VoiceOver support for all interactive elements
- Dynamic Type support
- Minimum touch target: 44x44 points

### Localization
- Initial language: English
- RTL support consideration

### Security
- Secure credential storage (Keychain)
- Certificate pinning for API calls
- No sensitive data in logs

## Out of Scope (v1.0)
- [Feature/capability explicitly excluded]

## Technical Constraints
- iOS 17.0+ required
- Swift 6.0 with strict concurrency
- SwiftUI only (no UIKit)
- SwiftData for persistence

## Timeline
| Phase | Duration | Deliverables |
|-------|----------|--------------|
| Foundation | Week 1-2 | Core architecture, navigation |
| Core Features | Week 3-6 | Main functionality |
| Polish | Week 7-8 | UI/UX refinement |
| Launch | Week 9-10 | Testing, App Store |

## Open Questions
- [ ] Question 1
- [ ] Question 2
```

## Process
1. Interview stakeholders (or gather requirements)
2. Define user personas
3. Prioritize features (P0 = must have, P1 = should have, P2 = nice to have)
4. Set measurable success criteria
5. Document constraints and assumptions
6. Get approval before implementation