Prd Writer

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:

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

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

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

12. Open Questions and Decisions

13. Appendix

Workflow

Step 1: Gather Information

Ask clarifying questions (one at a time):

1. What is the product/feature being defined?
2. Who is the target user/persona?
3. What problem does it solve?
4. What are the key success metrics?
5. What are the main features?
6. Any constraints or dependencies?

Step 2: Draft PRD

Create PRD in sections, validating each:

1. Header and DACE(R)
2. Problem statements
3. Goals and features
4. Use cases and requirements
5. 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