acceptance-validator

Validate completed work against acceptance criteria and architecture constraints.

8|4|Updated Feb 7, 2026

Search Tags:#automation #validation #QA #acceptance-testing #architecture-check #story-management

Ready to run

npx skills add https://github.com/adrien-barret/claude-kit --skill acceptance-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-validator
Source: https://github.com/adrien-barret/claude-kit/tree/main/project-template/.claude/skills/acceptance-validator
Command: npx skills add https://github.com/adrien-barret/claude-kit --skill acceptance-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces that completed work satisfies acceptance criteria, aligns with the architecture design, and meets customer requirements, acting as a quality gate before stories are marked as passed.

Core Features & Use Cases

Acceptance criteria validation: verify all criteria are implemented and covered by tests.
Architecture compliance: check against architecture guidance (e.g., .claude/output/architecture.yaml) when present to ensure API contracts, data models, and surface areas match the design.
Evidence-driven gating: generate PASS/FAIL results with verifiable evidence and link relevant test results.

Quick Start

Use the validator on a completed story artifact to automatically confirm it meets defined criteria and is ready for review.

Frequently Asked Questions about acceptance-validator

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

FAQPage Schema

How do I automate acceptance criteria validation in a software delivery pipeline?▼

Automate acceptance validation by reading criteria from story artefacts, inspecting code and tests, running the test suite, and reporting PASS or FAIL with evidence. This gates stories, features, or tasks before release across code reviews and documentation.

Can I verify architecture compliance against architecture.yaml during acceptance testing?▼

Yes, acceptance validation verifies architecture constraints via architecture.yaml when present. It ensures API contracts, data models, and surface areas match the design before a story is marked as passed.

How do I gate completed stories before release using automated QA checks?▼

Gate completed stories by running an automated validator that checks completed work against acceptance criteria, architecture design, and customer requirements, generating evidence-driven PASS or FAIL results with links to relevant test results.

Does acceptance validation work without invoking an AI model?▼

Yes, the validation process respects the disable-model-invocation setting to avoid AI model usage entirely. It relies on inspecting code, running tests, and reading story artefacts to produce PASS or FAIL outcomes.

What evidence is generated when acceptance criteria validation reports a failure?▼

When validation reports a FAIL, it generates verifiable evidence and links relevant test results. This evidence-driven gating confirms whether all criteria are implemented and covered by tests before review.

When do I need automated acceptance validation for feature releases?▼

You need automated acceptance validation when you require a QA gate to enforce that completed work satisfies acceptance criteria, aligns with architecture design, and meets customer requirements before stories are marked as passed.