requirements-analysis
Waterfall Phase 1 - Requirements Analysis (需求分析)
When & Why to Use This Skill
This Claude skill automates the foundational phase of the Waterfall software development lifecycle by streamlining requirements analysis. It helps users transform raw ideas into structured documentation, including markdown specifications, user stories, and Gherkin feature files, while enforcing a formal 'Review Gate' to ensure stakeholder alignment and scope stability before development begins.
Use Cases
- Software Project Initiation: Converting initial stakeholder discussions into formal requirement documents (docs/specs) with clear user stories and acceptance criteria.
- BDD (Behavior Driven Development) Scaffolding: Automatically generating Gherkin .feature files and directory structures to bridge the gap between business requirements and automated testing.
- Scope Governance: Implementing a mandatory review process to freeze requirements, preventing scope creep and ensuring all parties agree on the 'Phase 1' deliverables before proceeding to design.
| name | requirements analysis |
|---|---|
| description | Waterfall Phase 1 - Requirements Analysis (需求分析) |
Phase 1: Requirements Analysis
Gate: 必須完成需求文件才能進入下一階段
Gather Requirements User, 請描述您的需求。我會幫您整理成正式的需求文件。
Create Requirements Document
mkdir -p docs/specs touch docs/specs/FEATURE_NAME-requirements.mdDocument Requirements I will create/update
docs/specs/FEATURE_NAME-requirements.mdwith:- User Stories
- Acceptance Criteria
- Non-functional requirements
Create Gherkin Feature Files (框架)
mkdir -p e2e/featuresI will create
.featurefiles with:- Feature description (As a... I want... So that...)
- Scenario titles only (不含 Given/When/Then 細節)
範例:
Feature: Blog CMS As a blogger I want to create posts Scenario: Create a new blog post Scenario: Publish a draft postReview Gate User, 請審閱:
docs/specs/requirements.mde2e/features/*.feature(Scenario 標題)
您必須明確說「需求批准」才能進入 Phase 2 (系統設計)。 ⚠️ 進入下一階段後,需求將被凍結。