verification-before-completion

Prevent false positive completion claims in CI/CD by enforcing a strict verification gate that requires running specific commands and reading their output before asserting any build success or bug resolution.

Incomplete code ships after bug fixes when developers rely on assumptions instead of concrete evidence, requiring a mandatory verification process to confirm tests pass and no new issues arise before completion.

Enforce evidence-based verification before deployment by applying a defined gate function involving command identification, execution, reading output, and strict verification of the results prior to any success assertions.

Verify a bug fix before committing code by running the relevant test suite, confirming the specific bug is no longer present in the output, and checking that no newly introduced issues have arisen.

Yes, you can use this verification process for all stages of software development, from initial coding to final deployment, ensuring that concrete evidence strictly precedes any claims of task completion.

Relying on assumptions for build verification leads to costly errors and premature completion claims, making it necessary to mandate executing commands and checking output to maintain development honesty.