verification-loop

To enforce spec conformance and prevent silent failures before a PR, run a verification loop that executes prioritized checks for build, typecheck, lint, tests, and security while auditing exported symbols against specification documents.

A TDD gate prevents test-first process skipping by verifying the TDD sequencing artifact via a .tdd_lock file, ensuring developers followed the correct test-driven development sequence and blocking integration if gate skipping or confirmation bias is detected.

You run prioritized quality checks across security, build, and linting phases by executing the verification script with a priority flag, allowing you to sequence checks from P0 through P10 to catch critical security and build failures before lower priority lint issues.

Yes, you can detect spec drift between specification documents and API routes automatically through the spec conformance audit, which flags divergence by comparing exported symbols, API routes, and referenced files against the defined specification.

The best way to catch silent failure patterns in AI-assisted code is to use silent-failure hunting, which flags common patterns that hide broken behavior even when CI appears green, ensuring deterministic verification gates block PR creation for flawed implementations.

Yes, you need a .tdd_lock file to enforce TDD sequence during code review cycles, as the verification loop requires this sequencing artifact to verify that the test-first process was followed and to prevent developers from bypassing the TDD gate.