verification-before-completion

To enforce verification before a pull request, apply a strict protocol requiring the execution of fresh test, lint, and build commands, objectively analyzing their output before making any task completion claims.

The best way to prevent rationalizing skipped quality assurance is to apply a verification gatekeeping framework that identifies and rejects common excuses, mandating verifiable evidence for all success assertions.

Yes, agent-based task delegation requires fresh verification command execution to ensure technical accuracy, preventing agents from claiming work is finished without running full verification protocols and analyzing the output.

Verify work completion claims objectively by running full, fresh verification commands and analyzing their output directly, ensuring that all status assertions in the software development workflow are backed by verifiable evidence.

You need evidence-based verification whenever making task completion assertions, submitting pull requests, or delegating agent-based tasks, ensuring technical accuracy by running full verification commands before claiming success.

Relying on assumptions for completion status lacks verifiable evidence, creating a common pitfall where work is claimed as finished without actual proof, leading to unverified technical accuracy and potential workflow failures.