Verification Before Completion

To prevent premature claims of task completion, enforce a strict verification process mandating the execution and review of fresh evidence like test command output before any success is declared.

Verify code review success by identifying the command that proves your claim, running it fresh, reading the output, and confirming the evidence shows zero failures before declaring completion.

Rework from broken work happens when developers prioritize assumptions over evidence. Catching issues requires mandatory verification of test output and build logs before committing or merging code.

The best way to enforce quality assurance before claiming a bug is fixed is to mandate the execution of relevant test suites and verify the output confirms zero failures prior to declaring success.

Mandatory verification does not require specific testing frameworks. It enforces a process of running and reviewing evidence like build logs or test commands to ensure work is genuinely correct.

An evidence-based verification process should not be bypassed when declaring any task completion, as skipping it risks dishonesty, trust issues, and shipping incomplete or broken work to your team.