PRD Writer
Create comprehensive Product Requirements Documents following the Intuit PRD template format. This skill ensures consistent, well-structured PRDs that align with Intuit's product development standards.
When to Use
- User explicitly asks for a PRD
- User wants to document product requirements
- User needs to formalize a product idea into a structured document
- User mentions "product requirements", "PRD", or "spec"
PRD Structure (Intuit Template)
1. Header Section
🚧 Draft | ✅ Approved | 🔄 In Review
LAST UPDATED: [Date]
[PRD Title]
[One-line description of initiative for quick context]
2. PRD DACE(R) Table
Governance table for decision-making:
| ROLE |
NAMES |
REVIEW STATUS |
| DRIVER (Drive decision process) |
PM (Primary Owner): [Name], PD: [Name], PE: [Name], XD: [Name] |
Not started |
| APPROVER (Ultimate decision authority) |
[Name] |
Not started |
| CONSULTED (Contribute input) |
[Names] |
Not started |
| ESCALATION PATH |
[Name] |
Not started |
| (REVIEWERS) |
[Names] |
Not started |
3. Background & Current State
- Current state experience with pain points
- Industry data and competitive landscape
- Link to recordings, Figma files, or other references
4. Problem Statements (D4D Framework)
Use the D4D problem statement framework:
Customer Problem:
I am… [narrow description of customer]
I am trying to… [desired outcome]
But… [problem or barrier]
Because… [root cause]
Which makes me feel… [emotion]
Business Problem:
I am… [business unit/team]
I am trying to… [business goal]
But… [challenge]
Because… [root cause]
Which makes me feel… [impact]
5. Ideal State
In a perfect world: [Vision of solved problem]
The biggest benefit to me is: [Primary value proposition]
Which makes me feel: [Emotional outcome]
6. Business Goals and Success Metrics
| GOAL/METRIC |
DESCRIPTION |
TARGET |
| [Metric name] |
[Brief description] |
[Target value] |
7. Key Features
High-level explanation of feature areas (3-6 features):
- Feature 1: [Description]
- Feature 2: [Description]
- Feature 3: [Description]
8. Use Cases & Functional Requirements
| ID |
PRIORITY |
PERSONA |
USE CASE |
ACCEPTANCE CRITERIA |
| 1.1 |
P0/P1/P2 |
[Persona] |
[As a user, I want...] |
[Criteria for completion] |
Priority levels:
- P0: Must have for launch
- P1: Important, should have
- P2: Nice to have
9. Non-Functional Requirements
- Performance Requirements: Latency, throughput, scalability
- Security Requirements: Auth, encryption, compliance
- Legal Requirements: Disclaimers, regulatory compliance
- Internationalization: Language, locale support
- Reliability: Uptime SLA, failover
10. Insights and Problem Validation
- Market Research: SWOT analysis, competitive UI analysis
- Customer Insights: FMH findings, survey data, VOC, app reviews
- Include supporting quotes when available
11. Milestones and Releases
| MILESTONE |
TARGET DATE |
DESCRIPTION |
| Alpha |
[Date] |
[Scope] |
| Beta |
[Date] |
[Scope] |
| GA |
[Date] |
[Scope] |
12. Open Questions and Decisions
| TYPE |
DESCRIPTION |
PERSON RESPONSIBLE |
STATUS |
DATE TO CLOSE |
| Question/Decision |
[Description] |
[Name] |
Not started/Decided |
[Date] |
13. Appendix
| RELATED ARTIFACTS |
DESCRIPTION |
LINKS |
| Related PRD |
Connected workstream PRDs |
[Link] |
| Figma |
E2E journeys, wireframes, designs |
[Link] |
| XD Research |
Research plans and insights |
[Link] |
Workflow
Step 1: Gather Information
Ask clarifying questions (one at a time):
- What is the product/feature being defined?
- Who is the target user/persona?
- What problem does it solve?
- What are the key success metrics?
- What are the main features?
- Any constraints or dependencies?
Step 2: Draft PRD
Create PRD in sections, validating each:
- Header and DACE(R)
- Problem statements
- Goals and features
- Use cases and requirements
- Milestones and appendix
Step 3: Output Options
- Google Doc: Use
create_document and write_document tools
- Local Markdown: Write to project directory
- Both: Create local source of truth + shareable Google Doc
Best Practices
- Be specific: Avoid vague requirements; include measurable criteria
- Use personas: Reference specific user personas consistently
- Prioritize ruthlessly: Not everything is P0
- Include rationale: Explain "why" not just "what"
- Link evidence: Reference research, data, and prior art
- Keep it current: Update last modified date with each change
Agentic PRD Extensions
For AI-powered products, include additional sections:
- Agent Classification: Type, autonomy level, interaction mode
- AI Trust Profile: Data sensitivity, decision risk, reversibility
- AI Leverage Points: Where AI adds unique value
- Guardrails & Safety: Ethical bounds, fallbacks, human escalation
- Eval Framework: How to measure AI performance
See references/agentic-prd-template.md for detailed agentic PRD structure.
Quick Reference
| Section |
Purpose |
Key Content |
| DACE(R) |
Governance |
Who decides, approves, reviews |
| Problem Statement |
Why |
Customer and business pain points |
| Ideal State |
Vision |
Perfect world outcome |
| Goals/Metrics |
Success |
Measurable targets |
| Use Cases |
What |
Functional requirements |
| NFRs |
How |
Performance, security, reliability |
| Milestones |
When |
Timeline and phases |
1---2name: prd-writer-33description: "Use this skill when user asks to create, write, or draft a PRD (Product Requirements Document). Generates structured PRDs following Intuit template format with DACE(R) governance, problem statements (D4D framework), business goals, use cases, and functional requirements."4metadata:5 source: https://skillmd.com/skills/sach1ng/prd-writer-36---78# PRD Writer910Create comprehensive Product Requirements Documents following the Intuit PRD template format. This skill ensures consistent, well-structured PRDs that align with Intuit's product development standards.1112## When to Use1314- User explicitly asks for a PRD15- User wants to document product requirements16- User needs to formalize a product idea into a structured document17- User mentions "product requirements", "PRD", or "spec"1819## PRD Structure (Intuit Template)2021### 1. Header Section2223```24🚧 Draft | ✅ Approved | 🔄 In Review25LAST UPDATED: [Date]2627[PRD Title]28[One-line description of initiative for quick context]29```3031### 2. PRD DACE(R) Table3233Governance table for decision-making:3435| ROLE | NAMES | REVIEW STATUS |36|------|-------|---------------|37| DRIVER (Drive decision process) | PM (Primary Owner): [Name], PD: [Name], PE: [Name], XD: [Name] | Not started |38| APPROVER (Ultimate decision authority) | [Name] | Not started |39| CONSULTED (Contribute input) | [Names] | Not started |40| ESCALATION PATH | [Name] | Not started |41| (REVIEWERS) | [Names] | Not started |4243### 3. Background & Current State4445- Current state experience with pain points46- Industry data and competitive landscape47- Link to recordings, Figma files, or other references4849### 4. Problem Statements (D4D Framework)5051Use the D4D problem statement framework:5253**Customer Problem:**54```55I am… [narrow description of customer]56I am trying to… [desired outcome]57But… [problem or barrier]58Because… [root cause]59Which makes me feel… [emotion]60```6162**Business Problem:**63```64I am… [business unit/team]65I am trying to… [business goal]66But… [challenge]67Because… [root cause]68Which makes me feel… [impact]69```7071### 5. Ideal State7273```74In a perfect world: [Vision of solved problem]75The biggest benefit to me is: [Primary value proposition]76Which makes me feel: [Emotional outcome]77```7879### 6. Business Goals and Success Metrics8081| GOAL/METRIC | DESCRIPTION | TARGET |82|-------------|-------------|--------|83| [Metric name] | [Brief description] | [Target value] |8485### 7. Key Features8687High-level explanation of feature areas (3-6 features):88- Feature 1: [Description]89- Feature 2: [Description]90- Feature 3: [Description]9192### 8. Use Cases & Functional Requirements9394| ID | PRIORITY | PERSONA | USE CASE | ACCEPTANCE CRITERIA |95|----|----------|---------|----------|---------------------|96| 1.1 | P0/P1/P2 | [Persona] | [As a user, I want...] | [Criteria for completion] |9798Priority levels:99- **P0**: Must have for launch100- **P1**: Important, should have101- **P2**: Nice to have102103### 9. Non-Functional Requirements104105- **Performance Requirements**: Latency, throughput, scalability106- **Security Requirements**: Auth, encryption, compliance107- **Legal Requirements**: Disclaimers, regulatory compliance108- **Internationalization**: Language, locale support109- **Reliability**: Uptime SLA, failover110111### 10. Insights and Problem Validation112113- **Market Research**: SWOT analysis, competitive UI analysis114- **Customer Insights**: FMH findings, survey data, VOC, app reviews115- Include supporting quotes when available116117### 11. Milestones and Releases118119| MILESTONE | TARGET DATE | DESCRIPTION |120|-----------|-------------|-------------|121| Alpha | [Date] | [Scope] |122| Beta | [Date] | [Scope] |123| GA | [Date] | [Scope] |124125### 12. Open Questions and Decisions126127| TYPE | DESCRIPTION | PERSON RESPONSIBLE | STATUS | DATE TO CLOSE |128|------|-------------|-------------------|--------|---------------|129| Question/Decision | [Description] | [Name] | Not started/Decided | [Date] |130131### 13. Appendix132133| RELATED ARTIFACTS | DESCRIPTION | LINKS |134|-------------------|-------------|-------|135| Related PRD | Connected workstream PRDs | [Link] |136| Figma | E2E journeys, wireframes, designs | [Link] |137| XD Research | Research plans and insights | [Link] |138139## Workflow140141### Step 1: Gather Information142143Ask clarifying questions (one at a time):1441. What is the product/feature being defined?1452. Who is the target user/persona?1463. What problem does it solve?1474. What are the key success metrics?1485. What are the main features?1496. Any constraints or dependencies?150151### Step 2: Draft PRD152153Create PRD in sections, validating each:1541. Header and DACE(R)1552. Problem statements1563. Goals and features1574. Use cases and requirements1585. Milestones and appendix159160### Step 3: Output Options161162- **Google Doc**: Use `create_document` and `write_document` tools163- **Local Markdown**: Write to project directory164- **Both**: Create local source of truth + shareable Google Doc165166## Best Practices167168- **Be specific**: Avoid vague requirements; include measurable criteria169- **Use personas**: Reference specific user personas consistently170- **Prioritize ruthlessly**: Not everything is P0171- **Include rationale**: Explain "why" not just "what"172- **Link evidence**: Reference research, data, and prior art173- **Keep it current**: Update last modified date with each change174175## Agentic PRD Extensions176177For AI-powered products, include additional sections:178179- **Agent Classification**: Type, autonomy level, interaction mode180- **AI Trust Profile**: Data sensitivity, decision risk, reversibility181- **AI Leverage Points**: Where AI adds unique value182- **Guardrails & Safety**: Ethical bounds, fallbacks, human escalation183- **Eval Framework**: How to measure AI performance184185See `references/agentic-prd-template.md` for detailed agentic PRD structure.186187## Quick Reference188189| Section | Purpose | Key Content |190|---------|---------|-------------|191| DACE(R) | Governance | Who decides, approves, reviews |192| Problem Statement | Why | Customer and business pain points |193| Ideal State | Vision | Perfect world outcome |194| Goals/Metrics | Success | Measurable targets |195| Use Cases | What | Functional requirements |196| NFRs | How | Performance, security, reliability |197| Milestones | When | Timeline and phases |