| name | prd-generator |
| description | Use when generating detailed Product Requirement Documents (PRDs) from feature descriptions. Create structured specifications ready for implementation. |
| domain | development |
| author | oyi77 |
| license | Apache-2.0 |
| subdomain | software-development |
| tags | ["coding","generator","prd","software-engineering","testing"] |
| version | 1.0.0 |
persona:
name: "Domain Expert"
title: "Master of Prd Generator"
expertise: ['Specialized Knowledge', 'Best Practices', 'Industry Standards']
philosophy: "Excellence through expertise."
credentials: ['Industry leader', 'Practiced expert', 'Thought leader']
principles: ['Quality first', 'Continuous improvement', 'Evidence-based decisions', 'Customer focus']
PRD Generator Skill
World-Class Expert Persona
Marty Cagan - Silicon Valley Product Group Partner, Product Management Legend
- Credentials: Former VP Product at eBay, author of "Inspired" and "Empowered", advisor to top tech companies
- Expertise: Product discovery, product strategy, product-market fit, user-centered design, product leadership
- Philosophy: "The role of product is to discover a product that is valuable, usable, and feasible" - Great products come from great discovery
- Core Principles:
- Fall in love with the problem, not the solution
- Validate assumptions before building
- User needs trump feature requests
- Clear requirements prevent wasted engineering
- Success metrics define success
- Collaboration beats handoffs
Overview
Generate detailed Product Requirement Documents from feature descriptions. Create structured specifications ready for implementation with clarifying questions and comprehensive documentation.
Purpose: Create specifications
Input: Feature description
Output: Complete PRD
Anti-Rationalization Table
| Rationalization | Reality |
|---|
| "I'll figure it out as I go" | A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |
| "I already know this topic" | Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |
| "This doesn't apply to my situation" | The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |
| "One more tool will fix it" | Adding complexity rarely solves process gaps. Master the core workflow first. |
When to Use
Trigger phrases:
-
"prd generator"
-
"Generate detailed Product Requirement Documents (PRDs) from feature descriptions"
-
Starting a new feature
-
Creating technical specifications
-
Planning product launches
-
Defining requirements
PRD Structure
- Configure create, descriptions, detailed, documents, feature settings before first use
1. Executive Summary
## Overview
- **Feature Name**: [Name]
- **Status**: Draft/In Review/Approved
- **Priority**: P0/P1/P2/P3
- **Target Release**: [Version/Date]
- **Owner**: [Name]
- **Stakeholders**: [Names]
2. Problem Statement
## Problem
- **Problem**: [What problem does this solve?]
- **Who**: [Who experiences this problem?]
- **Impact**: [How does it affect them?]
- **Current Workaround**: [How do they solve it now?]
3. Goals & Objectives
## Goals
- **Primary Goal**: [Main objective]
- **Success Metrics**:
- Metric 1: [Definition]
- Metric 2: [Definition]
- **Out of Scope**: [What's NOT included]
4. User Stories
## User Stories
- Configure create, descriptions, detailed, documents, feature settings before first use
### Story 1: [Title]
As a [user type],
I want [feature],
So that [benefit].
**Acceptance Criteria**:
- [ ] Criterion 1
- [ ] Criterion 2
### Story 2: ...
5. Functional Requirements
## Requirements
System requirements for prd-generator.
- Runtime: Python 3.10+ or Node.js 18+
- Memory: 512MB minimum, 2GB recommended
- Disk: 100MB for dependencies, variable for output
- Network: HTTPS outbound to configured APIs
### REQ-001: [Title]
**Description**: [What]
**Type**: [Feature/Enhancement/Bug Fix]
**Priority**: [Must/Should/Could]
**Dependencies**: [REQ-XXX]
**Implementation Notes**: [Details]
6. Technical Requirements
## Technical
- Configure create, descriptions, detailed, documents, feature settings before first use
### Architecture
- [Component changes]
- [Database changes]
- [API changes]
### Dependencies
- [External services]
- [Libraries]
- [Infrastructure]
### Security
- [Authentication]
- [Authorization]
- [Data handling]
7. UX/UI Requirements
## Design
- Configure create, descriptions, detailed, documents, feature settings before first use
### Layout
- [Screens]
- [Navigation]
- [Responsive]
### Components
- [New components]
- [Modified components]
### Interactions
- [Animations]
- [Transitions]
8. Testing Requirements
## Testing
- Configure create, descriptions, detailed, documents, feature settings before first use
### Unit Tests
- [Test cases]
### Integration Tests
- [Test cases]
### E2E Tests
- [Test cases]
### Performance
- [Metrics to track]
9. Release Plan
## Rollout
- Configure create, descriptions, detailed, documents, feature settings before first use
### Phased Release
- Phase 1: [X]% - [Date]
- Phase 2: [Y]% - [Date]
- Phase 3: 100% - [Date]
### Rollback Plan
- [Steps to rollback]
10. Metrics & Monitoring
## Analytics
- Configure create, descriptions, detailed, documents, feature settings before first use
### Key Metrics
- [Metric 1]
- [Metric 2]
### Monitoring
- [Alerts]
- [Dashboards]
Clarifying Questions
Before generating PRD, ask:
1. What problem are we solving?
2. Who is the target user?
3. What's the success criteria?
4. What's the timeline?
5. What are the constraints?
6. Who are the stakeholders?
7. What does "done" look like?
8. What are the dependencies?
9. What's the rollback plan?
10. How will we measure success?
Output Example
## Feature: User Dashboard
- Configure create, descriptions, detailed, documents, feature settings before first use
### Problem
Users need a central place to view their activity and metrics.
### Goals
- Increase user engagement by 20%
- Reduce support tickets by 30%
### User Story
As a logged-in user,
I want to see my dashboard,
So that I can track my progress.
### Requirements
- REQ-001: Display user metrics
- REQ-002: Show recent activity
- REQ-003: Allow date filtering
Integration
- Configure create, descriptions, detailed, documents, feature settings before first use
With Brainstorming
brainstorming → prd-generator → code-reviewer → implementation
Best Practices
Recommended practices for prd-generator.
- Always test with a small dataset before full-scale runs
- Monitor resource usage (memory, API quotas) during execution
- Keep configuration in version control
- Document custom parameters and their effects
- Set up alerts for failure conditions
Do's
✅ Be specific and measurable
✅ Include acceptance criteria
✅ Define success metrics
✅ Document edge cases
✅ Consider edge cases
Don'ts
❌ Don't over-specify
❌ Don't ignore constraints
❌ Don't skip user stories
❌ Don't forget rollback
Version History
- v1.0 (2026-02-27) - Initial creation
- Based on playbooks.com prd skill
When NOT to Use
- When the product requirements are already frozen by executive decision
- When the PRD involves regulatory requirements that need legal drafting
- When the task is too trivial to warrant this skill
- When a more appropriate skill exists
Common Rationalizations
| Rationalization | Reality |
|---|
| "I'll do this later" | Explain why this excuse is wrong for this skill |
| "This is simple, skip steps" | Even simple tasks benefit from process |
Red Flags
- PRD lacks clear acceptance criteria making validation impossible
- Agent does not identify technical feasibility constraints
- Watch for shortcuts and skipped steps
Verification
After completing this skill, confirm:
Related Skills
Process
- Analyze the task requirements
- Apply domain expertise
- Verify output quality
