verification-before-completion

To enforce verification before completion in TDD, you require explicit verification commands to be run and results reviewed before making any claims of success. This ensures no claims of successful code are made without empirical evidence of success.

The best way to prevent false positives in development completion claims is to enforce a verification workflow that requires running necessary verification commands and reviewing their output before confirming work is complete.

The verification workflow functions by requiring developers to identify the necessary verification command, execute it, review the output, and confirm the success claim before proceeding. This enforces honesty by validating completion claims empirically.

This verification workflow is applicable in test-driven development (TDD) environments and any codebase where you need to validate completion claims by running explicit verification commands and reviewing the empirical results.

Common oversights when verifying work quality include failing to run the specified verification command, not reviewing the output, or claiming completion without empirical evidence of success. Properly following the verification steps prevents these issues.