mcpField
R
requirements-analysis

requirements-analysis

github.com/yinhunfeixueDevelopment465 installsUpdated 23w ago
Repository

About requirements-analysis

A development skill for analyzing and confirming requirements before software design. It structures requirements, clarifies scope and ambiguity, and gates progress on review.

Key features

  1. 01Structure requirements with Given/When/Then
  2. 02Flag and confirm unclear or risky items
  3. 03Define the MVP scope
  4. 04Split and write requirement documents
  5. 05Require review before the next stage

Use cases

  1. 01Turn raw descriptions into checkable requirements
  2. 02Confirm edge cases and scope boundaries
  3. 03Review requirements before software design

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/yinhunfeixue/software_development_skills --skill requirements-analysis

After installing, type/requirements-analysisin Claude Code to confirm it loaded.

Details

From the project README

需求分析与确认

依赖规范

#[[file:../rules/review-base.md]] #[[file:../rules/git-workflow.md]] #[[file:../rules/project-structure.md]]

目的

明确需求边界，确保无歧义、无遗漏，为设计提供可靠输入。

输入

  • 原始描述：需求方提供的文字、原型、口述，或对话上下文

步骤

每个步骤先输出标题，再输出结果

  • 需求整理：用 Given/When/Then 描述每条需求，检查漏洞、矛盾、缺少分支
  • 需求确认：标记不明确或有风险的需求点，逐一与需求方确认
  • 范围界定：明确 MVP 范围，排除本期不做的内容
  • 确认需求：手动模式下，输出需求清单和范围边界，等待开发者确认后再继续
  • 写入文档：每个需求或每类需求单独一个文件，创建入口文档引用所有需求文件（路径遵守 project-structure 文档存放规范）
  • 执行 review：遵守 review-base，通过后才进入下一阶段

输出

  • 需求清单：每条含 Given/When/Then
  • 范围边界：本期做什么、不做什么

Review 检查清单

  • Given/When/Then：每条需求完整，无逻辑漏洞
  • 无矛盾：无矛盾或冲突的需求
  • 边界覆盖：异常场景和边界情况已覆盖
  • 范围清晰：MVP 范围边界清晰

阶段结束

下一阶段：software-design

#[[file:../rules/stage-gate.md]]

Comments

Markdown supported