verification-before-completion

To verify code changes before claiming completion, you must execute fresh verification commands like tests, builds, and linting, then inspect the actual outputs to gather evidence before reporting success.

Evidence-based validation in a software workflow requires running commands that prove a requested status and inspecting their fresh outputs before making any claims about task completion, bug fixes, or readiness.

To prevent false completion claims by an AI agent, require it to independently run verification commands, inspect the outputs, and provide concrete evidence of the actual state before communicating success.

Yes, you can apply completion safety checks before commits, pull requests, and task handoffs by enforcing verification gates that require running tests, builds, and linting to confirm actual state.

Yes, verification before completion works without external dependencies by requiring the execution of available local verification commands and inspecting their outputs to validate status before asserting work is finished.