What specific patterns does this skill look for?

It checks for unique identifiers matching the REQ-* pattern and ensures they are properly formatted and linked to intent IDs (INT-*).

When should I use this skill?

It is best used as a quality gate before moving from the requirements phase to the design or implementation stages to prevent architectural rework.

How does it handle failed validations?

If checks fail, the skill provides a detailed report listing the specific requirements, line numbers, and actionable suggestions to fix the issues.

Can this skill detect subjective language?

Yes, it scans for vague terms like 'user-friendly,' 'fast,' or 'good' and suggests replacing them with specific, measurable metrics.

Requirements Quality Validator

Name: Requirements Quality Validator
Author: foolishimp

byfoolishimp

Seguridad y Pruebas

Validates software requirement documentation for clarity, testability, and traceability before moving to the design phase.

Acerca de

The validate-requirements skill acts as a comprehensive quality gate within the software development lifecycle (SDLC). It automatically scans requirement documentation to ensure every specification is uniquely identified, properly formatted, and includes measurable acceptance criteria. By identifying ambiguous language and verifying traceability back to user intent (INT-*), this skill helps teams prevent expensive rework and ensures that developers have a clear, testable roadmap before implementation begins.

Características Principales

Pass/Fail reporting with specific recommendations for fixes
0 GitHub stars
Automated detection of ambiguous terms like 'user-friendly' or 'fast'
Acceptance criteria validation for testability and measurability
Unique REQ-* key verification to prevent duplicates
Traceability auditing to link requirements to original intent

Casos de Uso

Pre-design phase quality gate to ensure documentation readiness
Auditing legacy documentation for testability and technical clarity
Standardizing requirement formats across large engineering teams

Acerca de

Características Principales

Pass/Fail reporting with specific recommendations for fixes
0 GitHub stars
Automated detection of ambiguous terms like 'user-friendly' or 'fast'
Acceptance criteria validation for testability and measurability
Unique REQ-* key verification to prevent duplicates
Traceability auditing to link requirements to original intent

Casos de Uso

Pre-design phase quality gate to ensure documentation readiness
Auditing legacy documentation for testability and technical clarity
Standardizing requirement formats across large engineering teams