npx skills add https://github.com/jamesrochabrun/skills --skill prd-generator生成遵循行业最佳实践的全面、结构良好的产品需求文档(PRD)。此技能帮助产品经理创建清晰、可操作的需求文档,以协调利益相关者并指导开发团队。
当用户请求创建 PRD 时(例如,“为用户认证功能创建一个 PRD”),请遵循以下工作流程:
在生成 PRD 之前,通过探索性对话收集基本信息:
所需信息:
需要询问的探索性问题:
1. 你想要解决什么问题?
2. 此功能的主要用户/受众是谁?
3. 关键的商业目标是什么?
4. 我们需要注意哪些技术限制吗?
5. 成功是什么样子的?你将如何衡量它?
6. 此功能的时间线是怎样的?
7. 明确不在范围内的是什么?
注意: 如果用户预先提供了详细的简报或需求,你可以跳过一些问题。对于缺失的关键信息,务必要求澄清。
使用 references/prd_template.md 中的标准 PRD 模板来创建结构良好的文档。PRD 应包含:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
对于每个主要需求,使用标准格式生成用户故事:
作为 [用户类型],
我想要 [操作],
以便 [收益/价值]。
验收标准:
- [具体的、可测试的标准 1]
- [具体的、可测试的标准 2]
- [具体的、可测试的标准 3]
参考 references/user_story_examples.md 以获取常见模式和最佳实践。
根据产品类型使用适当的指标框架:
有关每个框架的详细指导,请查阅 references/metrics_frameworks.md。
可选地运行验证脚本以确保 PRD 的完整性:
scripts/validate_prd.sh <prd_file.md>
此脚本检查:
用户请求: “为我们的移动应用添加深色模式创建一个 PRD”
执行步骤:
用户请求: “为改进我们的搜索功能编写需求”
执行步骤:
用户请求: “我需要一个用于新分析仪表板产品的 PRD”
执行步骤:
用户请求: “为一个小型错误修复功能创建一个轻量级 PRD”
执行步骤:
好的需求应具备:
避免:
应该:
不应该:
范围内部分:
范围外部分:
选择指标应:
典型的指标类别:
此技能支持不同的 PRD 格式:
标准 PRD - 完整全面的文档 精益 PRD - 为敏捷团队精简的格式 一页纸 - 执行摘要格式 技术 PRD - 以工程为重点的需求 设计 PRD - 以 UX/UI 为重点的需求
请求时指定格式:“为...创建一个精益 PRD”或“为...生成一个技术 PRD”
设计需求部分应包含:
应涉及:
PRD 应有助于:
分发清单:
根据客户反馈创建 PRD 时:
为公司战略计划创建 PRD 时:
为技术改进创建 PRD 时:
为合规性要求创建 PRD 时:
在最终确定 PRD 之前,请验证:
# 基本验证
scripts/validate_prd.sh my_prd.md
# 带有建议的详细输出
scripts/validate_prd.sh my_prd.md --verbose
# 仅检查特定部分
scripts/validate_prd.sh my_prd.md --sections "user-stories,metrics"
此技能包含捆绑资源:
# 用户:"为我们的 iOS 应用添加生物识别认证创建一个 PRD"
# 助手将:
# 1. 询问关于安全要求、用户画像、现有认证的探索性问题
# 2. 生成 PRD,涵盖:
# - 问题:密码繁琐、安全问题
# - 解决方案:Face ID / Touch ID 集成
# - 用户故事:启用生物识别、回退到密码、设置管理
# - 指标:采用率、登录成功率、支持工单
# - 技术:iOS Keychain、LocalAuthentication 框架
# - 风险:设备兼容性、用户隐私问题
# 3. 输出格式化的 Markdown PRD
# 用户:"为改进我们的结账流程转化率编写需求"
# 助手将:
# 1. 收集当前转化率和流失点的数据
# 2. 生成 PRD,包括:
# - 现状分析及指标
# - 建议的改进(访客结账、保存支付方式、进度指示器)
# - A/B 测试计划
# - 成功指标:转化率提升、结账时间
# - 每项改进的用户故事
# 3. 包含分阶段推出方法
# 用户:"我需要一个用于企业客户管理仪表板的 PRD"
# 助手将:
# 1. 识别 B2B 特定需求(多租户、权限、报告)
# 2. 生成全面的 PRD,包含:
# - 企业用户画像(管理员、经理、分析师)
# - 基于角色的访问控制需求
# - 报告和分析需求
# - 集成需求(SSO、SCIM)
# - 成功指标:客户采用率、管理员效率
# 3. 包含企业特定的考量(合规性、SLA)
问题:PRD 太长/太详细
解决方案:创建一个“精益 PRD”,重点关注问题、解决方案、验收标准和指标。将完整 PRD 留给主要计划。
问题:需求太模糊
解决方案:添加具体示例,使用具体数字,包含视觉参考。将“快”替换为“在 2 秒内加载”。
问题:利益相关者未协调一致
解决方案:尽早将 PRD 作为草案分享,纳入反馈,亲自演示,在开发开始前获得明确的签署。
问题:范围不断扩展
解决方案:积极使用“范围外”部分,为未来阶段创建单独的 PRD,将范围与时间线约束联系起来。
问题:工程师认为不可行
解决方案:在流程中更早地让工程团队参与,对解决方案方法保持灵活,关注问题而非实现。
每周安装量
514
仓库
GitHub 星标数
101
首次出现
2026年1月20日
安全审计
安装于
opencode466
gemini-cli441
codex440
github-copilot421
cursor403
kimi-cli380
Generate comprehensive, well-structured Product Requirements Documents (PRDs) that follow industry best practices. This skill helps product managers create clear, actionable requirements documents that align stakeholders and guide development teams.
When a user requests to create a PRD (e.g., "create a PRD for a user authentication feature"), follow this workflow:
Before generating the PRD, collect essential information through a discovery conversation:
Required Information:
Discovery Questions to Ask:
1. What problem are you trying to solve?
2. Who is the primary user/audience for this feature?
3. What are the key business objectives?
4. Are there any technical constraints we should be aware of?
5. What does success look like? How will you measure it?
6. What's the timeline for this feature?
7. What's explicitly out of scope?
Note: If the user provides a detailed brief or requirements upfront, you can skip some questions. Always ask for clarification on missing critical information.
Use the standard PRD template from references/prd_template.md to create a well-structured document. The PRD should include:
For each major requirement, generate user stories using the standard format:
As a [user type],
I want to [action],
So that [benefit/value].
Acceptance Criteria:
- [Specific, testable criterion 1]
- [Specific, testable criterion 2]
- [Specific, testable criterion 3]
Reference references/user_story_examples.md for common patterns and best practices.
Use appropriate metrics frameworks based on the product type:
Consult references/metrics_frameworks.md for detailed guidance on each framework.
Optionally run the validation script to ensure PRD completeness:
scripts/validate_prd.sh <prd_file.md>
This checks for:
User Request: "Create a PRD for adding dark mode to our mobile app"
Execution:
User Request: "Write requirements for improving our search functionality"
Execution:
User Request: "I need a PRD for a new analytics dashboard product"
Execution:
User Request: "Create a lightweight PRD for a small bug fix feature"
Execution:
Good Requirements Are:
Avoid:
DO:
DON'T:
In-Scope Section:
Out-of-Scope Section:
Choose Metrics That:
Typical Metric Categories:
The skill supports different PRD formats:
Standard PRD - Full comprehensive document Lean PRD - Streamlined for agile teams One-Pager - Executive summary format Technical PRD - Engineering-focused requirements Design PRD - UX/UI-focused requirements
Specify the format when requesting: "Create a lean PRD for..." or "Generate a technical PRD for..."
Design Requirements Section Should Include:
Should Address:
PRD Should Help:
Distribution Checklist:
When creating a PRD based on customer feedback:
When creating a PRD for a strategic company initiative:
When creating a PRD for technical improvements:
When creating a PRD for compliance requirements:
Before finalizing the PRD, verify:
# Basic validation
scripts/validate_prd.sh my_prd.md
# Verbose output with suggestions
scripts/validate_prd.sh my_prd.md --verbose
# Check specific sections only
scripts/validate_prd.sh my_prd.md --sections "user-stories,metrics"
This skill includes bundled resources:
# User: "Create a PRD for adding biometric authentication to our iOS app"
# Assistant will:
# 1. Ask discovery questions about security requirements, user personas, existing auth
# 2. Generate PRD covering:
# - Problem: Password friction, security concerns
# - Solution: Face ID / Touch ID integration
# - User stories: Enable biometric, fallback to password, settings management
# - Metrics: Adoption rate, login success rate, support tickets
# - Technical: iOS Keychain, LocalAuthentication framework
# - Risks: Device compatibility, user privacy concerns
# 3. Output formatted markdown PRD
# User: "Write requirements for improving our checkout flow conversion"
# Assistant will:
# 1. Gather data on current conversion rates and drop-off points
# 2. Generate PRD including:
# - Current state analysis with metrics
# - Proposed improvements (guest checkout, saved payment, progress indicator)
# - A/B test plan
# - Success metrics: Conversion rate increase, time to checkout
# - User stories for each improvement
# 3. Include phased rollout approach
# User: "I need a PRD for an admin dashboard for enterprise customers"
# Assistant will:
# 1. Identify B2B-specific requirements (multi-tenancy, permissions, reporting)
# 2. Generate comprehensive PRD with:
# - Enterprise user personas (admin, manager, analyst)
# - Role-based access control requirements
# - Reporting and analytics needs
# - Integration requirements (SSO, SCIM)
# - Success metrics: Customer adoption, admin efficiency
# 3. Include enterprise-specific considerations (compliance, SLAs)
Issue: PRD is too long/detailed
Solution: Create a "Lean PRD" focusing on problem, solution, acceptance criteria, and metrics. Reserve full PRD for major initiatives.
Issue: Requirements are too vague
Solution: Add specific examples, use concrete numbers, include visual references. Replace "fast" with "loads in under 2 seconds."
Issue: Stakeholders not aligned
Solution: Share PRD early as draft, incorporate feedback, present in person, get explicit sign-off before development starts.
Issue: Scope keeps expanding
Solution: Use "Out of Scope" section aggressively, create separate PRDs for future phases, tie scope to timeline constraints.
Issue: Engineers say it's not feasible
Solution: Involve engineering earlier in process, be flexible on solution approach, focus on problem not implementation.
Weekly Installs
514
Repository
GitHub Stars
101
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubFailSocketPassSnykPass
Installed on
opencode466
gemini-cli441
codex440
github-copilot421
cursor403
kimi-cli380
竞品拆解分析工具:使用 inference.sh CLI 进行结构化竞品研究与截图
7,400 周安装
Laravel 12 最佳实践指南:29条规则构建可扩展应用
492 周安装
Python Excel自动化:openpyxl库操作XLSX文件教程,创建编辑格式化电子表格
492 周安装
Drizzle ORM 数据库迁移指南:TypeScript 迁移优先开发工作流
492 周安装
智能外联草拟工具:基于调研的个性化邮件与LinkedIn消息生成器 | 销售与营销自动化
492 周安装
Oracle 到 PostgreSQL 数据库迁移计划自动生成工具 | .NET 解决方案分析
493 周安装
TanStack Table 无头数据表格 | Cloudflare Workers + D1 服务器端分页排序
493 周安装