verification-before-completion

To enforce verification before completion, mandate identifying, running, and reading the output of verification commands to ensure evidence precedes assertions. This strict protocol prevents premature declarations of success across all development stages, including testing, building, and bug fixing.

The best way to prevent premature claims of work completion is to enforce an evidence-based protocol that mandates running test suites and checking their output. This prevents rationalization and ensures zero failures are confirmed before asserting any success status in your CI/CD pipeline.

Assuming code changes are correct without testing leads to errors because it skips the mandatory verification of command outputs. Without strictly verifying that tests pass with zero failures, developers risk making premature declarations of completion that compromise code quality and trust.

Yes, the verification protocol applies to bug fixing and agent delegation. It enforces strict evidence-based checks across all stages of development, preventing agents or developers from expressing satisfaction or claiming a bug is fixed without reading the actual verification command output.

To stop rationalization when skipping verification steps, apply a strict protocol that provides clear counter-arguments against common excuses for skipping tests. It mandates evidence-based claims, ensuring you run and read verification command outputs before declaring any work done.