acceptance-validator

Evaluate stories against acceptance criteria, architecture, and integration requirements.

Updated Mar 24, 2026

Search Tags:#architecture #integration #validation #qa #evidence #acceptance #tests

Ready to run

npx skills add https://github.com/foutoucour/guitar-match --skill acceptance-validator-foutoucour

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-validator
Source: https://github.com/foutoucour/guitar-match/tree/main/.claude/skills/acceptance-validator
Command: npx skills add https://github.com/foutoucour/guitar-match --skill acceptance-validator-foutoucour

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate completed work against acceptance criteria, architecture design, and customer requirements. Use as a quality gate before marking stories as passed.

Core Features & Use Cases

Acceptance Criteria Check: For each criterion listed in the story, locate the code, verify completion, ensure tests exist, run the tests, and report PASS or FAIL with evidence.
Architecture Compliance: Read .claude/output/architecture.yaml (if it exists) and verify alignment with design; API contracts, data models, and no architectural drift.
Integration Check: Verify the story's code integrates with previously completed stories, shared interfaces, and that the full test suite passes with no regressions.
Output Format: Provide a structured PASS/FAIL report including evidence and remediation steps when failures are found.

Quick Start

Run acceptance-validator on the target story to verify all acceptance criteria, architecture alignment, and test results before marking it as passed.

Frequently Asked Questions about acceptance-validator

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

FAQPage Schema

How do I validate completed user stories against acceptance criteria and architecture design?▼

To validate completed user stories, the acceptance-validator evaluates each criterion, locates the implementation code, runs tests, and checks alignment with architecture.yaml to produce a clear PASS/FAIL verdict with supporting evidence.

How do I check for architectural drift and API contract compliance before passing a story?▼

Checking for architectural drift involves reading architecture.yaml to verify API contracts and data models, ensuring the story's code integrates with shared interfaces and previously completed stories without regressions.

How do I automate acceptance criteria checks and generate a remediation plan for failures?▼

Automating acceptance criteria checks requires running tests against the story's code, evaluating each criterion, and outputting a structured PASS/FAIL report that includes specific remediation steps when validation failures are found.

Does the acceptance validation process verify integration with previously completed stories?▼

Yes, acceptance validation verifies integration by ensuring the story's code integrates with previously completed stories and shared interfaces, running the full test suite to confirm there are no regressions.

What is the best way to gate stories by tests, architecture, and integration requirements?▼

The best way to gate stories is to apply validation across the project, evaluating acceptance criteria, verifying API contracts and data models, and running tests to output a structured PASS/FAIL report with evidence.

What format does the acceptance validation report use for evidence and remediation?▼

The acceptance validation report uses a structured PASS/FAIL format that explicitly includes evidence for the verdict and provides detailed remediation steps when failures are found.