verification-before-completion

To verify work completion, you must execute verification commands like tests, linters, and builds, then interpret their output to ensure your success claims are backed by concrete evidence.

A verification process for quality assurance acts as a gate function, requiring developers to run tests and examine build outputs before making any claims about task success or completion.

Common red flags signaling a lack of work verification include skipping test execution, ignoring linter failures, and making success claims without examining the actual command line output.

You can prevent rationalization when skipping quality assurance checks by applying predefined counterarguments to common excuses, enforcing a strict step-by-step verification gate before completion.

Yes, this verification approach applies to project management workflows by enforcing honesty and reliability in completion claims through evidence-based output examination before finalizing tasks.