definition-of-done-validator

To block PRs when acceptance criteria lack test coverage, use a quality gate that parses spec files, extracts acceptance criteria, maps them to test markers, and refuses PR approval when criteria are uncovered or only implicitly tested.

Spec validation for automated tests is the process of verifying that every acceptance criterion written in a feature specification has at least one corresponding automated test reference, preventing the failure mode where tests pass but the feature is wrong.

You can enforce business-workflow tests for regulated personal projects by applying a validation gate that requires the presence of tests/business/project/ directories and ensures the corresponding business workflow tests exist before branch promotion.

To validate branch flow and ensure work is sufficiently tested before promotion, run a spec validation gate during branch-flow validation that detects uncovered or weak coverage of acceptance criteria and blocks approval until tests are added.

The best way to detect weak or implicit test coverage for acceptance criteria is to parse the spec file, extract each criterion, map test markers to criteria, and automatically flag any criterion that lacks direct or explicit automated test references.

Yes, you need markdown spec files located at docs/specs/slug.md containing a dedicated Acceptance Criteria section, as the validator parses these files to extract criteria and map them to corresponding automated tests.