PRD Writing Expert

This skill helps write structured Product Requirements Documents (PRDs) using industry-standard frameworks.

Use Cases

(1) User mentions "PRD," "Product Requirements Document," "requirements document," "feature specification" (2) User asks to "write requirements," "draft requirements document," "define product requirements" (3) User is conducting product planning, feature definition, acceptance criteria formulation (4) User needs to document product decisions, requirements analysis, or user story writing.

Core Framework

A PRD document contains the following core modules:

1. Problem Statement

• Background and current state
• Pain point analysis
• Opportunity identification
• Target users

2. User Stories

• Format: "As a [role], I want to [action] so that [value]"
• Acceptance Criteria
• User journey mapping

3. Requirements Prioritization

• MoSCoW Method: Must-have / Should-have / Could-have / Won't-have
• Value-Complexity Matrix
• MVP scope definition

4. Success Metrics

• North Star Metric
• Key Results
• Monitoring metrics

Workflow

1. Requirement Clarification: Gather product background, target users, and business objectives
2. Problem Definition: Define the problem statement and business opportunity
3. User Stories: Write user stories and acceptance criteria
4. Prioritization: Prioritize requirements using the MoSCoW method
5. Metric Definition: Set success metrics and monitoring plans
6. Document Output: Generate a structured PRD document

Detailed Guides

• User Story Writing: See references/user-stories.md
• Requirements Prioritization Methods: See references/prioritization.md
• Success Metrics Framework: See references/metrics.md

Template Resources

• PRD Template: assets/prd-template.md

Usage Examples

Example 1: New Feature PRD User: "Help us write a PRD for the user login feature" → Output: A complete PRD including problem statement, user stories, requirement prioritization, and success metrics

Example 2: Product Iteration PRD User: "Need to define product requirements for shopping cart optimization" → Output: A structured PRD focused on shopping cart optimization, including user journey and acceptance criteria

Example 3: Documenting Product Decisions User: "Document our decision to abandon the social sharing feature" → Output: Product decision document including background, analysis, and decision outcome

Notes

• PRDs should be clear and actionable; avoid vague language
• Requirement prioritization should align with business objectives
• Success metrics should be quantifiable and trackable
• Acceptance criteria should be specific and testable