review-tests

To check test coverage against acceptance criteria, you need a gap analysis comparing spec files like prd.md and user-stories.md to the repository's test suite. This process identifies uncovered criteria and proposes surface tests to close those gaps.

Spec coverage gap analysis is the process of comparing feature specifications against existing tests to find missing scenarios. It works by inspecting test files and documentation to assess coverage, then proposing concrete surface tests for uncovered criteria.

Generating surface tests for untested user stories involves comparing user-stories.md to the test suite to find gaps, then proposing and generating targeted tests. This yields a structured plan including a criteria checklist and recommended tests.

Yes, you can audit test coverage using tech spec and PRD files by pointing the review process to the feature directory. It locates tech-spec.md, prd.md, and CONTEXT.md to derive criteria and assess whether existing tests cover the specified constraints.

Tracking test coverage regressions across multiple runs requires persisting a machine-parseable HTML coverage report after each audit. This historical tracking detects regressions by comparing previous coverage states to the current assessment.

No specific test framework is required, but the repository must contain a test suite and documentation files like prd.md and user-stories.md. The audit process inspects the existing tests and documentation to find coverage gaps independently of the framework.