spec-verify

Spec coverage verification maps public entrypoints, business-logic branches, and tests to corresponding spec entries. It classifies results as PASS or NEEDS_WORK based on predefined criteria, generating a structured markdown report with actionable remediation guidance.

Reverse spec coverage automates the validation of specification alignment before a feature release. You need it when you want to confirm that generated specs accurately describe intended behavior and surface gaps between your tests, codebase, and documentation.

Test-to-spec mapping analyzes your test suite and matches tests to spec criteria to surface unmapped tests. The process applies a 70% mapping threshold to classify results and outputs a detailed remediation report.

Branch coverage analysis requires 75% of domain logic branches to have corresponding spec scenarios, while entrypoint coverage requires 80% of public entrypoints to be mapped to spec entries to achieve a PASS classification.

Yes, optional deep-gap analysis prompts a deeper review of domain specs to surface ambiguities. This supplements the standard entrypoint, branch, and test coverage checks by identifying unclear specification definitions.

The automated reporting relies on fixed pass thresholds of 80% entrypoint, 75% branch, and 70% test-to-spec coverage. It outputs a static markdown file and cannot dynamically adjust criteria or integrate external testing frameworks beyond the repository scan.