PRD Writer

When to Use

• Starting a new feature or product initiative
• Need to document requirements for the engineering team
• Stakeholders need a detailed project overview
• Before beginning design or development work
• To align cross-functional teams on scope and goals

What This Skill Does

Creates structured, comprehensive PRDs covering problem statement, proposed solution, requirements, success metrics, and implementation details.

Instructions

Help me write a comprehensive PRD for [feature name]. Include:

1. Problem Statement

• Current situation
• User pain points
• Business impact

2. Proposed Solution

• Overview of the approach
• User stories
• Success metrics

3. Requirements

• Functional requirements
• Technical requirements
• Design requirements

4. Implementation

• Dependencies
• Timeline estimate
• Resources needed

5. Risks and Mitigations

Your context: [Add product context, feature details, and constraints here]

Best Practices

• Be specific about the problem and user pain points
• Include quantitative success metrics
• Define scope clearly (what's in scope and out of scope)
• Consider technical constraints upfront
• Add detailed user stories for key flows
• Include acceptance criteria

Example

Input: Building a notification center for SaaS app, target users are power users who miss important updates Output: Full PRD with problem statement, user stories, functional/technical requirements, success metrics (reduce missed notifications by 40%), timeline, and risk assessment