prd-writer
Focuses on generating comprehensive Product Requirements Documents (PRDs), clarifying product features, user stories, and acceptance criteria to ensure consistent product development direction.
npx skills add pmprompt/claude-plugin-product-management --skill prd-writerBefore / After Comparison
1 组Manually writing PRDs is time-consuming and labor-intensive. Document content may miss key requirements, and a chaotic structure can lead to misunderstandings by the development team, high project delay risks, and negatively impact product development efficiency.
Using a PRD generation tool automatically creates structured and comprehensive product requirements documents, ensuring clear and unambiguous requirements that cover all necessary elements, significantly improving product development efficiency and document quality.
description SKILL.md
name: prd-writer description: Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation. argument-hint: [feature name]
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
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:
- Problem Statement
- Current situation
- User pain points
- Business impact
- Proposed Solution
- Overview of the approach
- User stories
- Success metrics
- Requirements
- Functional requirements
- Technical requirements
- Design requirements
- Implementation
- Dependencies
- Timeline estimate
- Resources needed
- 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
Further Reading
forumUser Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill