majiayu000 PRD Writer Skill
This skill helps write comprehensive Product Requirements Documents (PRDs) for software projects.
When to Use
- When starting a new project
- When defining product features
- When documenting requirements
- When planning development roadmaps
- When communicating product vision
Capabilities
- Requirements Gathering: Help define user needs and business goals
- Feature Specification: Detail features and functionality
- User Stories: Write clear user stories and acceptance criteria
- Technical Specs: Define technical requirements and constraints
- Success Metrics: Define measurable success criteria
PRD Structure
A complete PRD includes:
- Executive Summary: High-level overview
- Problem Statement: What problem are we solving?
- Goals & Objectives: What are we trying to achieve?
- User Personas: Who are the users?
- Features & Requirements: What will we build?
- User Stories: How will users interact with it?
- Technical Requirements: What are the technical constraints?
- Success Metrics: How will we measure success?
- Timeline: When will it be delivered?
Usage Examples
Start a New PRD
I need to write a PRD for a task management application
Add Feature Requirements
Can you help me write requirements for a notification system?
Create User Stories
Write user stories for the authentication flow
Best Practices
- Start with the problem, not the solution
- Focus on user needs and outcomes
- Be specific and measurable
- Include acceptance criteria
- Consider edge cases and constraints