Back to Details

requirements-analyst

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Requirements Analyst

Requirements Analyst

将模糊需求转换为清晰、可执行的需求文档。
Convert vague requirements into clear, executable requirement documents.

如何使用

How to Use

触发方式

Trigger Method

直接向 Claude 描述你的需求，例如：
我需要一个用户登录功能
帮我分析这个需求：用户可以在平台上发布和浏览商品
写一份用户系统的 PRD
Describe your requirements directly to Claude, for example:
I need a user login function
Help me analyze this requirement: Users can post and browse products on the platform
Write a PRD for the user system

使用流程

Usage Process

  1. 描述需求 - 用自然语言描述你想要的功能（可以模糊、不完整）
  2. 选择格式 - 助手会询问输出格式（用户故事 / PRD）
  3. 回答问题 - 助手会提出澄清问题，选择或输入你的答案
  4. 获取文档 - 助手输出结构化的需求文档
  5. 确认调整 - 根据需要要求修改或补充
  1. Describe Requirements - Describe the function you want in natural language (can be vague or incomplete)
  2. Select Format - The assistant will ask about the output format (User Story / PRD)
  3. Answer Questions - The assistant will ask clarification questions, select or enter your answers
  4. Obtain Document - The assistant outputs a structured requirement document
  5. Confirm Adjustments - Request modifications or supplements as needed

示例对话

Example Conversation

用户输入：
我需要一个购物车功能
助手响应：
  1. 识别缺失信息（用户类型、功能范围、边界条件）
  2. 提出澄清问题：
    • 购物车是否支持游客使用？
    • MVP 需要哪些功能？（增删商品/保存/优惠券）
    • 有商品数量上限吗？
  3. 根据回答生成用户故事：
markdown
undefined
User Input:
I need a shopping cart function
Assistant Response:
  1. Identify missing information (user type, function scope, boundary conditions)
  2. Ask clarification questions:
    • Does the shopping cart support guest users?
    • What features are needed for MVP? (Add/remove items/save/coupons)
    • Is there a quantity limit for items?
  3. Generate User Story based on answers:
markdown
undefined

User Story: 添加商品到购物车

User Story: Add Product to Shopping Cart

As a 网站访客或注册用户 I want 将商品添加到购物车 So that 我可以继续浏览并稍后一起结账
As a website visitor or registered user I want to add products to the shopping cart So that I can continue browsing and checkout together later

Acceptance Criteria

Acceptance Criteria

  • Given 用户在商品详情页，when 点击"加入购物车"，then 商品被添加且显示成功提示
  • Given 购物车已有该商品，when 再次添加，then 数量增加而非重复添加
undefined
  • Given the user is on the product detail page, when clicking "Add to Cart", then the product is added and a success prompt is displayed
  • Given the product is already in the shopping cart, when adding again, then the quantity increases instead of adding a duplicate entry
undefined

分析工作流程

Analysis Workflow

Phase 1: 理解阶段

Phase 1: Understanding Stage

  1. 接收需求 - 读取用户提供的原始需求文本
  2. 识别关键要素:
    • 用户角色 (Who) - 明确或隐含的用户类型
    • 期望结果 (What) - 用户想要实现什么
    • 业务价值 (Why) - 为什么需要这个功能
    • 约束条件 - 技术、时间、资源限制
  3. 标记模糊点 - 识别需要澄清的部分
  1. Receive Requirements - Read the original requirement text provided by the user
  2. Identify Key Elements:
    • User Role (Who) - Explicit or implicit user types
    • Desired Outcome (What) - What the user wants to achieve
    • Business Value (Why) - Why this feature is needed
    • Constraints - Technical, time, resource limitations
  3. Mark Vague Points - Identify parts that need clarification

Phase 2: 澄清阶段

Phase 2: Clarification Stage

使用 AskUserQuestion 解决模糊点。按优先级提问：
  1. 关键未知 - 没有这个信息无法编写故事
  2. 范围澄清 - 边界条件和边缘情况
  3. 验收细节 - 如何验证功能完成
提问原则：
  • 批量提问 (3-5 个问题一组)
  • 提供选项而非开放式问题
  • 说明如果不回答会采用的默认假设
Use AskUserQuestion to resolve vague points. Ask questions by priority:
  1. Critical Unknowns - Cannot write the story without this information
  2. Scope Clarification - Boundary conditions and edge cases
  3. Acceptance Details - How to verify feature completion
Question Principles:
  • Ask in batches (3-5 questions per group)
  • Provide options instead of open-ended questions
  • Explain default assumptions if no answer is provided

Phase 3: 生成阶段

Phase 3: Generation Stage

根据选择的输出格式生成文档：
  • 用户故事: 按照 USER_STORY_TEMPLATE.md 生成
  • PRD: 按照 PRD_TEMPLATE.md 生成
Generate documents based on the selected output format:
  • User Story: Generated according to USER_STORY_TEMPLATE.md
  • PRD: Generated according to PRD_TEMPLATE.md

Phase 4: 确认阶段

Phase 4: Confirmation Stage

  • 使用 INVEST 检查清单验证故事完整性
  • 如果故事过大，提供拆分选项
  • 与用户确认并接受反馈
  • Use the INVEST checklist to verify story completeness
  • If the story is too large, provide splitting options
  • Confirm with the user and accept feedback

快速开始

Quick Start

典型需求分析流程：
  1. 用户提供模糊需求
  2. 助手识别缺失信息，提出澄清问题
  3. 用户回答问题
  4. 助手生成格式化用户故事和验收标准
Typical requirements analysis process:
  1. User provides vague requirements
  2. Assistant identifies missing information and asks clarification questions
  3. User answers the questions
  4. Assistant generates formatted User Stories and acceptance criteria

输出格式

Output Formats

用户故事格式

User Story Format

markdown
undefined
markdown
undefined

User Story: [简短标题]

User Story: [Short Title]

As a [用户类型/角色] I want [功能/能力] So that [价值/收益]
As a [User Type/Role] I want [Function/Capability] So that [Value/Benefit]

Acceptance Criteria

Acceptance Criteria

  • Given [上下文], when [操作], then [预期结果]
  • Given [上下文], when [操作], then [预期结果]
  • Given [Context], when [Action], then [Expected Result]
  • Given [Context], when [Action], then [Expected Result]

Notes

Notes

  • [假设说明]
  • [识别的依赖]
  • [排除范围]
undefined
  • [Assumption Explanations]
  • [Identified Dependencies]
  • [Excluded Scope]
undefined

PRD 格式

PRD Format

markdown
undefined
markdown
undefined

[产品/功能名称] PRD

[Product/Function Name] PRD

1. 概述

1. Overview

1.1 背景

1.1 Background

[为什么要做这个功能]
[Why this feature is needed]

1.2 目标

1.2 Objectives

[业务目标和用户目标]
[Business and user objectives]

1.3 成功指标

1.3 Success Metrics

[如何衡量成功]
[How to measure success]

2. 用户分析

2. User Analysis

2.1 目标用户

2.1 Target Users

[用户画像]
[User personas]

2.2 用户痛点

2.2 User Pain Points

[当前问题]
[Current problems]

2.3 用户场景

2.3 User Scenarios

[典型使用场景]
[Typical usage scenarios]

3. 功能需求

3. Functional Requirements

3.1 功能列表

3.1 Feature List

[功能清单和优先级]
[Feature list and priorities]

3.2 功能详情

3.2 Feature Details

[每个功能的详细说明]
[Detailed description of each feature]

3.3 用户故事

3.3 User Stories

[对应的用户故事]
[Corresponding user stories]

4. 非功能需求

4. Non-Functional Requirements

[性能/安全/兼容性要求]
[Performance/security/compatibility requirements]

5. 数据需求

5. Data Requirements

[数据模型和流转]
[Data model and flow]

6. 开放问题

6. Open Issues

[待决策事项]
undefined
[Pending decisions]
undefined

参考资料

Reference Materials

用户故事模板

User Story Template

何时加载: 生成用户故事时
参见 USER_STORY_TEMPLATE.md:
  • 标准用户故事格式
  • INVEST 检查清单
  • 故事拆分策略
When to Load: When generating User Stories
See USER_STORY_TEMPLATE.md:
  • Standard User Story format
  • INVEST checklist
  • Story splitting strategies

PRD 模板

PRD Template

何时加载: 生成 PRD 文档时
参见 PRD_TEMPLATE.md:
  • 完整 PRD 结构
  • 各部分编写指南
  • PRD vs 用户故事对比
When to Load: When generating PRD documents
See PRD_TEMPLATE.md:
  • Complete PRD structure
  • Guidelines for each section
  • PRD vs User Story comparison

验收标准指南

Acceptance Criteria Guide

何时加载: 编写验收标准时
参见 ACCEPTANCE_CRITERIA.md:
  • Given-When-Then 格式
  • 不同类型验收标准示例
  • 编写原则
When to Load: When writing acceptance criteria
See ACCEPTANCE_CRITERIA.md:
  • Given-When-Then format
  • Examples of different types of acceptance criteria
  • Writing principles

提问策略

Questioning Strategy

何时加载: 需要向用户提问时
参见 CLARIFICATION_QUESTIONS.md:
  • 何时提问 vs 何时假设
  • 按类别分类的问题库
  • 问题模板
When to Load: When needing to ask users questions
See CLARIFICATION_QUESTIONS.md:
  • When to ask vs when to assume
  • Categorized question library
  • Question templates