mcpField
R
requirements-analysis

requirements-analysis

github.com/dralgorhythmDevelopment130200 installsUpdated 15w ago
Repository

About requirements-analysis

Requirements Analysis is a skill for structuring and validating software requirements. It covers requirement types, root-cause questioning, SMART criteria, edge cases, and documentation with acceptance criteria.

Key features

  1. 01Classify functional and non-functional needs
  2. 02Apply five-whys analysis
  3. 03Assess requirements with SMART criteria
  4. 04Explore edge cases and constraints
  5. 05Validate and document acceptance criteria

Use cases

  1. 01Clarify the underlying need behind a request
  2. 02Review requirements for testability and completeness
  3. 03Document features with acceptance criteria

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill requirements-analysis

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

Details

From the project README

Requirements Analysis

Requirement Types

Functional Requirements

What the system should DO.

  • "Users can log in with email and password"
  • "System sends order confirmation email"
Non-Functional Requirements

How the system should BEHAVE.

  • Performance: "Page loads in < 2 seconds"
  • Security: "Passwords stored with bcrypt"
  • Scalability: "Supports 10,000 concurrent users"
Constraints

Limitations on the solution.

  • "Must use existing authentication system"
  • "Must run on AWS"

Analysis Techniques

Ask "Why?" Five Times

Uncover the real requirement.

Requirement: "Add export to Excel button"
Why? → "Users need to share reports"
Why? → "Finance reviews monthly sales"
Why? → "They compare against targets"
Why? → "To identify underperforming regions"
Real Need: Regional performance dashboard
SMART Criteria

Requirements should be:

  • Specific: Clear and unambiguous
  • Measurable: Can verify completion
  • Achievable: Technically feasible
  • Relevant: Aligned with goals
  • Time-bound: Has deadline
Edge Case Analysis
  • What happens with no data?
  • What happens with too much data?
  • What if the user is offline?
  • What if permissions are denied?

Requirement Validation

  • Is it testable?
  • Is it achievable?
  • Is it necessary?
  • Is it consistent with other requirements?
  • Is it complete?
  • Is the priority clear?

Documenting Requirements

**REQ-001**: User Authentication

**Description**: Users must authenticate to access the system.

**Acceptance Criteria**:
1. Given valid credentials, user gains access
2. Given invalid credentials, user sees error
3. After 5 failed attempts, account is locked

**Priority**: Must Have
**Dependencies**: REQ-002 (User Management)

Comments

Markdown supported