verification-before-completion

To enforce verification before completion, you must require fresh evidence from executed test, build, or analysis commands. This prevents unsupported claims by ensuring agents validate implementation results and accurately report observed outcomes before asserting success.

Yes, verification gates apply directly to code review and pull requests by requiring executed commands to prove status. Agents must run and review the specific checks that validate generated code, commits, and requirement completion before making assertions.

The best way to prevent unsupported completion claims in CI workflows is enforcing verification gates that require running tests and builds. This ensures agents report accurate, observed results from executed commands instead of unverified success assertions.

To verify code generation and requirement checks, you must execute specific validation commands and review the fresh evidence. This process ensures completion claims are backed by observed test, build, and analysis results before reporting success.

Agents report tasks as finished without verification when lacking enforced completion gates. Requiring fresh evidence from executed tests, builds, and analysis commands prevents unsupported success claims by mandating observed result validation before status reporting.

Yes, verification before completion works for quality assurance and testing workflows by guiding agents through validating tests, builds, and analysis results. It requires running appropriate commands and reviewing observed evidence before declaring requirement completion.