requirements-validator

Validate software implementations against user requirements and project specifications.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/GuilhermeSoares009/supplier-eval-system --skill requirements-validator-guilhermesoares009
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements-validator
Source: https://github.com/GuilhermeSoares009/supplier-eval-system/tree/main/skills/requirements-validator
Command: npx skills add https://github.com/GuilhermeSoares009/supplier-eval-system --skill requirements-validator-guilhermesoares009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that the software or code developed precisely matches the user's requirements and project specifications, preventing costly rework and ensuring user satisfaction.

Core Features & Use Cases

  • Requirement Analysis: Breaks down user prompts into atomic, verifiable requirements.
  • Implementation Verification: Checks if the developed code fulfills each identified requirement.
  • Gap Identification: Pinpoints missing functionalities or deviations from specifications.
  • Use Case: After a developer implements a new feature based on a user story, this Skill can be used to systematically check if all acceptance criteria have been met before deployment.

Quick Start

Validate that the implemented code for the user story 'US-123' meets all specified functional and non-functional requirements.

Frequently Asked Questions about requirements-validator

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

FAQPage Schema
How do I validate code against user requirements before deployment?

To validate code against user requirements, you need to break down project specifications into atomic items and verify implementation correctness. This process checks feature existence and completeness to identify deviations and ensure compliance with functional criteria.

How do I verify if my implementation meets all functional and non-functional criteria?

Verifying implementation against functional and non-functional criteria involves analyzing prompts for atomic requirements and edge cases. This systematically checks if developed features fulfill each identified constraint and pinpoints missing items for gap closure.

What is the best way to check user story acceptance criteria after implementing a feature?

Checking user story acceptance criteria involves systematically verifying that the newly developed code fulfills every specified requirement. This implementation verification identifies missing functionalities and suggests improvements to ensure full compliance before release.

Can I use requirements validation to identify missing functionalities and edge cases in my code?

Yes, requirements validation identifies missing functionalities and edge cases by analyzing project specifications for atomic constraints. It pinpoints deviations from the expected implementation and suggests improvements to achieve complete feature correctness and compliance.

Why does my software implementation deviate from the original project specifications?

Software implementation deviates from project specifications when atomic requirements are missed during development. Requirement analysis systematically verifies existence and correctness, identifying exact gaps and constraints that prevent your code from meeting user needs.

Does requirements validation work for checking compliance with non-functional project constraints?

Yes, requirements validation works for checking compliance with non-functional project constraints by analyzing prompts to extract atomic requirements. It verifies the correctness and existence of features against all specified functional and non-functional criteria to ensure completeness.