Requirements Discovery Specification

Exploratory discovery process, analyzes projects from multi-role perspectives to inspire users to identify high-ROI functional directions.

⚠️ Core Mandatory Requirements

Automatic Trigger Conditions

• 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. 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 Behavior Requirements

Execute When Triggered

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

💡 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

Connection with w02-task-planning

Confirmed Feature: [Feature Name], would you like to execute /w02-task-planning for detailed planning?

Collaboration with W00 (Automatic + Manual)

• 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

  - Detailed identification rules for trigger signals

• references/role-play-method.md

  - Role-playing methods and practices

• references/roi-evaluation.md

  - ROI evaluation framework