QE Requirements Validation

Validate software requirements by assessing SMART acceptance criteria and generating traceability matrices.

1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/aquariuscook/Agent_Modus_Map --skill qe-requirements-validation-aquariuscook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: QE Requirements Validation
Source: https://github.com/aquariuscook/Agent_Modus_Map/tree/main/.claude/skills/qe-requirements-validation
Command: npx skills add https://github.com/aquariuscook/Agent_Modus_Map --skill qe-requirements-validation-aquariuscook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the critical challenge of ensuring software requirements are well-defined, traceable, and cover all necessary scenarios, preventing costly rework and ensuring product quality.

Core Features & Use Cases

  • Acceptance Criteria Validation: Checks requirements against SMART principles (Specific, Measurable, Achievable, Relevant, Testable) and identifies ambiguities.
  • Requirements Traceability: Builds matrices to link requirements to test cases, code, and documentation, highlighting coverage gaps.
  • BDD Scenario Generation: Creates Behavior-Driven Development (BDD) scenarios in Gherkin format from user stories.
  • Coverage Analysis: Assesses the completeness of requirements coverage by tests and identifies areas needing attention.
  • Use Case: A product manager can use this Skill to automatically validate acceptance criteria for all user stories in a sprint, ensuring they are clear and testable before development begins.

Quick Start

Validate the acceptance criteria for the current sprint's user stories.

Frequently Asked Questions about QE Requirements Validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate acceptance criteria against SMART principles?

Validating acceptance criteria against SMART principles involves analyzing requirements to ensure they are Specific, Measurable, Achievable, Relevant, and Testable, while identifying ambiguities to guarantee completeness before development.

How do I generate BDD scenarios in Gherkin format from user stories?

Generating BDD scenarios from user stories translates requirements into Gherkin format, creating structured Behavior-Driven Development test cases that ensure software requirements are unambiguous and fully testable.

Can I pull software requirements directly from Jira for coverage analysis?

Yes, you can pull software requirements directly from Jira. The Skill integrates with Jira for requirement sourcing, enabling automated coverage analysis and validation of user stories.

What is a requirements traceability matrix and how does it prevent coverage gaps?

A requirements traceability matrix links requirements to test cases, code, and documentation, systematically highlighting coverage gaps to prevent costly rework and ensure product quality.

What's the best way to assess requirements coverage for a sprint?

Assessing requirements coverage for a sprint requires analyzing user stories to identify coverage gaps in tests, ensuring acceptance criteria are complete, unambiguous, and testable before development begins.