prd-writer
包括的な製品要求仕様書（PRD）の生成に特化し、製品機能、ユーザーストーリー、受け入れ基準を明確にし、製品開発の方向性の一貫性を確保します。
npx skills add pmprompt/claude-plugin-product-management --skill prd-writerBefore / After 効果比較
1 组手動でのPRD作成は時間と労力がかかり、ドキュメント内容に重要な要件の漏れや構造の混乱が生じる可能性があります。これにより、開発チームの理解にずれが生じ、プロジェクト遅延のリスクが高まり、製品開発効率に悪影響を与えます。
PRD生成ツールを使用することで、構造化された包括的な製品要求仕様書が自動的に作成されます。これにより、要件が明確で曖昧さがなく、必要なすべての要素が網羅され、製品開発効率とドキュメント品質が大幅に向上します。
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
forumユーザーレビュー (0)
レビューを書く
レビューなし
統計データ
ユーザー評価
この Skill を評価