Back to Details

w01-requirement-discovery

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

需求发现规范

Requirements Discovery Specification

探索性发现流程，通过多角色视角分析项目，启发用户识别高ROI功能方向。
Exploratory discovery process, analyzes projects from multi-role perspectives to inspire users to identify high-ROI functional directions.

⚠️ 核心强制要求

⚠️ Core Mandatory Requirements

自动触发条件

Automatic Trigger Conditions

检测到以下信号时必须触发：
  • 用户询问："有哪些功能？"、"应该做什么？"、"优先级？"、"下一步？"
  • 用户表达迷茫、不确定的语气
  • 用户要求"梳理任务"、"分析需求"、"探索方向"
Must trigger when detecting the following signals:
  • When the user asks: "What features are there?", "What should I do?", "Priority?", "Next step?"
  • User expresses confused or uncertain tone
  • User requests "sort out tasks", "analyze requirements", "explore directions"

发现流程

Discovery Process

  1. 项目分析：快速理解项目定位、当前状态、技术栈
  2. 角色扮演：从目标用户/开发者/维护者视角分析
  3. 需求生成：列出高ROI必须实现的功能
  4. ROI评估：按影响范围 × 实现成本排序
  5. 启发输出：对话式呈现，不生成文档
  1. Project Analysis: Quickly understand project positioning, current status, and tech stack
  2. Role-Playing: Analyze from the perspectives of target users/developers/maintainers
  3. Requirements Generation: List high-ROI must-implement features
  4. ROI Evaluation: Sort by impact scope × implementation cost
  5. Inspirational Output: Present in conversational format, no documents generated

AI Agent 行为要求

AI Agent Behavior Requirements

触发时执行

Execute When Triggered

  1. 快速分析项目：理解项目定位、核心价值、当前状态
  2. 推荐角色：根据项目类型推荐角色（用户/开发者/维护者）
  3. 角色扮演：假设自己是目标角色，列出"必须实现的高ROI功能"
  4. ROI评估：每个功能标注影响范围、实现成本、优先级
  5. 对话式输出：以启发式对话呈现，不生成文档
  1. Quickly Analyze the Project: Understand project positioning, core value, and current status
  2. Recommend Roles: Recommend roles (user/developer/maintainer) based on project type
  3. Role-Playing: Assume the target role and list "must-implement high-ROI features"
  4. ROI Evaluation: Mark each feature with impact scope, implementation cost, and priority
  5. Conversational Output: Present in an inspirational conversational format, no documents generated

输出格式

Output Format

💡 需求发现

从 [角色] 视角分析，当前项目最应该优先实现：

1. [功能名] - ROI: ⭐⭐⭐⭐⭐
   - 影响范围：[用户价值/技术价值/维护价值]
   - 实现成本：[低/中/高]
   - 优先级：P0/P1/P2

2. [功能名] - ROI: ⭐⭐⭐⭐
   ...

建议：选择功能后执行 /w02-task-planning 进行详细规划
💡 Requirements Discovery

From the perspective of [Role], the top priority features to implement for the current project are:

1. [Feature Name] - ROI: ⭐⭐⭐⭐⭐
   - Impact Scope: [User Value/Technical Value/Maintenance Value]
   - Implementation Cost: [Low/Medium/High]
   - Priority: P0/P1/P2

2. [Feature Name] - ROI: ⭐⭐⭐⭐
   ...

Suggestion: After selecting a feature, execute /w02-task-planning for detailed planning

衔接 w02-task-planning

Connection with w02-task-planning

用户确认功能后，提示：
已确认功能：[功能名]，是否执行 /w02-task-planning 进行详细规划？
When the user confirms the feature, prompt:
Confirmed Feature: [Feature Name], would you like to execute /w02-task-planning for detailed planning?

与 W00 协同（自动 + 手动）

Collaboration with W00 (Automatic + Manual)

  • 方向确认且预计跨会话执行时，由主流程阶段完成 issue 初始化/绑定，再调用 
    w00-workflow-checkpoint
    写首个 checkpoint。
  • 用户手动调用 
    /w00-workflow-checkpoint
    时，聚焦存档/读档，不负责初始化。
  • When the direction is confirmed and cross-session execution is expected, the main process stage completes issue initialization/binding, then calls 
    w00-workflow-checkpoint
    to write the first checkpoint.
  • When the user manually calls 
    /w00-workflow-checkpoint
    , focus on saving/loading checkpoints, and do not take responsibility for initialization.

参考资料

Reference Materials

  • references/trigger-signals.md
    - 触发信号详细识别规则
  • references/role-play-method.md
    - 角色扮演方法与实践
  • references/roi-evaluation.md
    - ROI评估框架
  • references/trigger-signals.md
    - Detailed identification rules for trigger signals
  • references/role-play-method.md
    - Role-playing methods and practices
  • references/roi-evaluation.md
    - ROI evaluation framework