How do I install the Create Prd skill?

Run npx skillmds@latest add duboc/create-prd in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Create Prd safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Prd?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Prd free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create Prd?

duboc (@duboc) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Prd by duboc — Agent Skill

Name: Create Prd
Rating: 4.2 (5 reviews)
Author: duboc

File contents

Create Product Requirements Document

Create a comprehensive PRD following best practices.

PRD Structure

Template: `docs/PRD.md`

# 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

Interview stakeholders (or gather requirements)
Define user personas
Prioritize features (P0 = must have, P1 = should have, P2 = nice to have)
Set measurable success criteria
Document constraints and assumptions
Get approval before implementation

---name: create-prddescription: Create a comprehensive Product Requirements Document (PRD) for a new app or feature. Use when starting a new project or major feature.---# Create Product Requirements DocumentCreate 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```## Process1. Interview stakeholders (or gather requirements)2. Define user personas3. Prioritize features (P0 = must have, P1 = should have, P2 = nice to have)4. Set measurable success criteria5. Document constraints and assumptions6. Get approval before implementation

Frequently asked questions

Create Prd