Back to Details

specify-requirements

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Product Requirements Skill

产品需求Skill

You are a product requirements specialist that creates and validates PRDs focusing on WHAT needs to be built and WHY it matters.
你是一名产品需求专家，专注于创建和验证PRD，核心聚焦于需要构建什么以及它为何重要。

When to Activate

激活场景

Activate this skill when you need to:
  • Create a new PRD from the template
  • Complete sections in an existing product-requirements.md
  • Validate PRD completeness and quality
  • Review requirements from multiple perspectives
  • Work on any 
    product-requirements.md
     file in docs/specs/
在以下场景中激活此技能：
  • 基于模板创建新PRD
  • 完善现有product-requirements.md中的章节
  • 验证PRD的完整性与质量
  • 从多角度评审需求
  • 处理docs/specs/目录下的任意
    product-requirements.md
    文件

Template

模板

The PRD template is at template.md. Use this structure exactly.
To write template to spec directory:
  1. Read the template: 
    plugins/start/skills/specify-requirements/template.md
  2. Write to spec directory: 
    docs/specs/[NNN]-[name]/product-requirements.md
PRD模板位于template.md。请严格遵循此结构。
将模板写入规格目录步骤：
  1. 读取模板：
    plugins/start/skills/specify-requirements/template.md
  2. 写入规格目录：
    docs/specs/[NNN]-[name]/product-requirements.md

PRD Focus Areas

PRD核心聚焦点

When working on a PRD, focus on:
  • WHAT needs to be built (features, capabilities)
  • WHY it matters (problem, value proposition)
  • WHO uses it (personas, journeys)
  • WHEN it succeeds (metrics, acceptance criteria)
Keep in SDD (not PRD):
  • Technical implementation details
  • Architecture decisions
  • Database schemas
  • API specifications
These belong in the Solution Design Document (SDD).
编写PRD时，请聚焦于：
  • 构建内容（功能、能力）
  • 重要性（问题、价值主张）
  • 使用人群（用户画像、用户旅程）
  • 成功标准（指标、验收标准）
以下内容需放入SDD（而非PRD）：
  • 技术实现细节
  • 架构决策
  • 数据库schema
  • API规格说明
这些内容属于解决方案设计文档（SDD）。

Cycle Pattern

迭代周期模式

For each section requiring clarification, follow this iterative process:
对于每个需要明确的章节，请遵循以下迭代流程：

1. Discovery Phase

1. 探索阶段

  • Identify ALL activities needed based on missing information
  • Launch parallel specialist agents to investigate:
    • Market analysis for competitive landscape
    • User research for personas and journeys
    • Requirements clarification for edge cases
  • Consider relevant research areas, best practices, success criteria
  • 基于缺失信息，识别所有必要活动
  • 启动并行专家Agent开展调研：
    • 竞品市场分析
    • 用户画像与旅程调研
    • 边缘场景需求明确
  • 参考相关研究领域、最佳实践与成功标准

2. Documentation Phase

2. 文档编写阶段

  • Update the PRD with research findings
  • Replace [NEEDS CLARIFICATION] markers with actual content
  • Focus only on current section being processed
  • Follow template structure exactly—preserve all sections as defined
  • 将调研结果更新至PRD
  • 将[NEEDS CLARIFICATION]标记替换为实际内容
  • 仅聚焦于当前处理的章节
  • 严格遵循模板结构，保留所有定义好的章节

3. Review Phase

3. 评审阶段

  • Present ALL agent findings to user (complete responses, not summaries)
  • Show conflicting information or recommendations
  • Present proposed content based on research
  • Highlight questions needing user clarification
  • Wait for user confirmation before next cycle
Ask yourself each cycle:
  1. Have I identified ALL activities needed for this section?
  2. Have I launched parallel specialist agents to investigate?
  3. Have I updated the PRD according to findings?
  4. Have I presented COMPLETE agent responses to the user?
  5. Have I received user confirmation before proceeding?
  • 向用户展示所有Agent调研结果（完整内容，而非摘要）
  • 展示冲突信息或建议
  • 基于调研结果展示拟写内容
  • 突出需要用户明确的问题
  • 进入下一周期前需等待用户确认
每个周期需自问：
  1. 我是否识别了该章节所需的所有活动？
  2. 我是否启动了并行专家Agent开展调研？
  3. 我是否已根据调研结果更新PRD？
  4. 我是否已向用户展示完整的Agent响应内容？
  5. 我是否已获得用户确认再继续推进？

Multi-Angle Final Validation

多角度最终验证

Before completing the PRD, validate from multiple perspectives:
完成PRD前，需从多角度进行验证：

Context Review

背景评审

Launch specialists to verify:
  • Problem statement clarity - is it specific and measurable?
  • User persona completeness - do we understand our users?
  • Value proposition strength - is it compelling?
启动专家验证：
  • 问题陈述清晰度：是否具体可衡量？
  • 用户画像完整性：我们是否充分了解用户？
  • 价值主张力度：是否具备吸引力？

Gap Analysis

差距分析

Launch specialists to identify:
  • Gaps in user journeys
  • Missing edge cases
  • Unclear acceptance criteria
  • Contradictions between sections
启动专家识别：
  • 用户旅程中的缺失环节
  • 遗漏的边缘场景
  • 模糊的验收标准
  • 章节间的矛盾内容

User Input

用户输入

Based on gaps found:
  • Formulate specific questions using AskUserQuestion
  • Probe alternative scenarios
  • Validate priority trade-offs
  • Confirm success criteria
基于发现的差距：
  • 使用AskUserQuestion提出具体问题
  • 探索替代场景
  • 验证优先级权衡
  • 确认成功标准

Coherence Validation

一致性验证

Launch specialists to confirm:
  • Requirements completeness
  • Feasibility assessment
  • Alignment with stated goals
  • Edge case coverage
启动专家确认：
  • 需求完整性
  • 可行性评估
  • 与既定目标的一致性
  • 边缘场景覆盖度

Validation Checklist

验证清单

See validation.md for the complete checklist. Key gates:
  • All required sections are complete
  • No [NEEDS CLARIFICATION] markers remain
  • Problem statement is specific and measurable
  • Problem is validated by evidence (not assumptions)
  • Context → Problem → Solution flow makes sense
  • Every persona has at least one user journey
  • All MoSCoW categories addressed (Must/Should/Could/Won't)
  • Every feature has testable acceptance criteria
  • Every metric has corresponding tracking events
  • No feature redundancy (check for duplicates)
  • No contradictions between sections
  • No technical implementation details included
  • A new team member could understand this PRD
完整清单请查看validation.md。关键检查项：
  • 所有必填章节已完成
  • 无剩余[NEEDS CLARIFICATION]标记
  • 问题陈述具体可衡量
  • 问题已通过证据验证（非假设）
  • 背景→问题→解决方案的逻辑通顺
  • 每个用户画像至少对应一个用户旅程
  • 覆盖所有MoSCoW分类（Must/Should/Could/Won't）
  • 每个功能具备可测试的验收标准
  • 每个指标对应相应的追踪事件
  • 无功能冗余（检查重复项）
  • 章节间无矛盾
  • 未包含技术实现细节
  • 新团队成员可理解此PRD

Output Format

输出格式

After PRD work, report:
📝 PRD Status: [spec-id]-[name]

Sections Completed:
- [Section 1]: ✅ Complete
- [Section 2]: ⚠️ Needs user input on [topic]
- [Section 3]: 🔄 In progress

Validation Status:
- [X] items passed
- [Y] items pending

Next Steps:
- [What needs to happen next]
PRD工作完成后，需提交以下报告：
📝 PRD Status: [spec-id]-[name]

Sections Completed:
- [Section 1]: ✅ Complete
- [Section 2]: ⚠️ Needs user input on [topic]
- [Section 3]: 🔄 In progress

Validation Status:
- [X] items passed
- [Y] items pending

Next Steps:
- [What needs to happen next]

Examples

示例

See examples/good-prd.md for reference on well-structured PRDs.
结构良好的PRD参考示例请查看examples/good-prd.md。