acceptance-validator

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.

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.

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.

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.

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.

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.