mcpField
R
Requirements Validation

Requirements Validation

github.com/danhvbTesting & quality108 installs
Repository

About Requirements Validation

A requirements validation skill for business analysts, developers, and stakeholders to check that requirements are clear, complete, consistent, testable, and aligned with business needs before development. It combines reviews, prototyping, acceptance-criteria checks, and traceability.

Key features

  1. 01Peer reviews and stakeholder sign-off
  2. 02UI/UX prototyping for validation
  3. 03Acceptance criteria review
  4. 04Requirements traceability matrix
  5. 05INVEST user-story checklist
  6. 06Ambiguity and conflict handling

Use cases

  1. 01Review requirements before development begins
  2. 02Validate UI/UX expectations with mockups
  3. 03Link requirements to designs and tests

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/danhvb/my-ba-skills --skill requirements-validation

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

Details

From the project README

Requirements Validation Skill

Purpose

Ensure that the requirements are correct, complete, consistent, and actually solve the business problem before development begins. "Building the right thing" vs. "Building the thing right".

Verification vs. Validation

  • Verification: "Are we building the product right?" (Does the Requirement meet quality standards?)
  • Validation: "Are we building the right product?" (Does the Requirement solve the user's need?)

Key Validation Techniques

1. Peer Review / Walkthroughs
  • Process: Informal or semi-formal review with colleagues (Devs, other BAs).
  • Goal: Find logic errors, ambiguities, and missing edge cases.
  • Checklist:
    • Is it clear?
    • Is it testable?
    • Is it feasible?
2. Stakeholder Inspections / Sign-off
  • Process: Formal review with Business Owners.
  • Goal: Approval to proceed.
  • Method: Don't just read the doc. Walk through scenarios/examples.
3. Prototyping
  • Method: Show, don't tell. Use wireframes or mockups.
  • Goal: Validate UI/UX requirements. "Is this what you imagined?"
4. Acceptance Criteria Review
  • Method: Review "Given-When-Then" scenarios.
  • Goal: Ensure the requirement is specific enough to be tested.

Requirements Traceability Matrix (RTM)

Purpose

Link Requirements to their origin and downstream deliverables.

  • Forward Traceability: Requirement → Design → Code → Test. (Ensures everything required is built).
  • Backward Traceability: Test → Requirement → Business Goal. (Ensures no "Gold Plating" / unnecessary features).
RTM Template
Req IDDescriptionSource (Stakeholder)Business GoalDesign DocTest Case IDStatus
FR-01Guest CheckoutMarketing VPIncrease ConvDD-CheckoutTC-001, 002Implemented
FR-02Apple PayCEOMobile StrategyDD-PaymentTC-005Approved
FR-033D SecureComplianceLegal ReqsDD-SecurityTC-010Tested

Quality Checklist (INVEST)

For User Stories:

  • Independent
  • Negotiable
  • Valuable
  • Estimable
  • Small
  • Testable

Handling Validation Issues

  1. Ambiguity: "System must be fast."
    • Fix: "System must load in < 2s."
  2. Conflict: Stakeholder A wants Blue, B wants Red.
    • Fix: Facilitate negotiation or escalate to Sponsor.
  3. Incompleteness: Missing error states.
    • Fix: Ask "What happens if this fails?"

Output

  • Validated Requirements Package: Clean, approved docs.
  • Sign-off Artifact: Email or digital signature approving the scope.
  • Updated Traceability Matrix.

Tools

  • Jira (Linking Stories to Epics/Tests).
  • Excel/Lark Base (RTM).
  • Confluence/Lark Docs (Approvals).

Comments

Markdown supported