// "Guides product managers through creating comprehensive PRDs via structured conversation. Adapts depth and format based on project complexity—from quick feature specs to full product requirements with compliance considerations."
| name | prd |
| description | Guides product managers through creating comprehensive PRDs via structured conversation. Adapts depth and format based on project complexity—from quick feature specs to full product requirements with compliance considerations. |
Help product managers create implementation-ready Product Requirements Documents through structured conversation. This skill adapts its approach based on project complexity, regulatory context, and organizational needs.
Respond to requests like:
Before generating any PRD content, gather essential context through targeted questions. Never assume—ask.
Required Context (always gather):
Conditional Context (gather when relevant):
Based on gathered context, classify the project:
Lightweight Spec — Use for:
Standard PRD — Use for:
Comprehensive PRD — Use for:
Adapt the PRD structure to match project scope:
# [Feature Name] Specification
## Overview
Brief description of what this feature does and why it matters.
## User Story
As a [user type], I want [capability] so that [benefit].
## Requirements
### Functional Requirements
- FR-1: [Requirement]
- FR-2: [Requirement]
### Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Technical Notes
Any implementation considerations or constraints.
## Out of Scope
What this feature explicitly does NOT include.
# [Product/Feature Name] PRD
## Executive Summary
One paragraph: what, why, and expected impact.
## Problem Statement
- Current state and pain points
- Who is affected
- Cost of inaction
## Goals & Success Metrics
| Goal | Metric | Target |
|------|--------|--------|
| [Goal 1] | [How measured] | [Target value] |
## User Personas
### Primary: [Persona Name]
- Role/Context
- Goals
- Pain points
### Secondary: [Persona Name]
- Role/Context
- Goals
- Pain points
## Requirements
### Functional Requirements
Organized by epic or capability area:
**[Epic 1 Name]**
- FR-1.1: [Requirement] | Priority: [Must/Should/Could]
- FR-1.2: [Requirement] | Priority: [Must/Should/Could]
**[Epic 2 Name]**
- FR-2.1: [Requirement] | Priority: [Must/Should/Could]
### Non-Functional Requirements
- Performance: [Specific targets]
- Security: [Requirements]
- Scalability: [Expectations]
- Accessibility: [Standards to meet]
## User Flows
Describe key user journeys through the system.
## Dependencies & Constraints
- Technical dependencies
- Business constraints
- Timeline considerations
## Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
## Out of Scope
Explicit boundaries for this version.
## Open Questions
Items requiring further discussion or decision.
Includes everything in Standard PRD, plus:
## Compliance & Regulatory
- Applicable regulations (HIPAA, GDPR, SOC2, FedRAMP, FISMA, etc.)
- Compliance requirements mapped to features
- Audit and reporting needs
- Data residency requirements
## Security Requirements
- Authentication/Authorization requirements
- Data classification and handling
- Encryption requirements (at rest, in transit)
- Audit logging requirements
## Change Management
- Impact on existing users/workflows
- Migration strategy
- Training requirements
- Rollback plan
## Stakeholder Sign-off
| Stakeholder | Role | Approval Status | Date |
|-------------|------|-----------------|------|
## Appendices
- Detailed technical specifications
- Compliance mapping documents
- Integration specifications
Before finalizing, verify each requirement against these criteria:
Clarity Check:
Completeness Check:
Feasibility Check:
Conclude PRD generation by explicitly noting:
User: "Help me create a PRD for a dashboard"
Response approach:
When generating the final PRD: