verification-before-completion

Enforcing verification commands requires running specific tests and reviewing their output before making any success claims. This process ensures evidence-based accuracy and prevents false completions by requiring proof of work before finalizing.

Preventing false claims involves implementing evidence-based verification steps that mandate running validation commands. This enforces honesty in software workflows by requiring developers to review actual command output before claiming a task is complete.

Requiring evidence for completion claims involves enforcing the execution of verification commands and checking their output. This mechanism prevents dishonesty by ensuring that all success claims are backed by concrete data.

Process enforcement for work completion applies broadly to software development workflows to ensure honesty and accuracy. It functions by requiring verification commands to run and their output to be reviewed before any completion claims are made.

Running verification commands before claiming completion prevents false claims and avoids unnecessary reworks. It enforces honesty by requiring you to review the actual output and back your success claims with evidence.

Enforcing verification before completion relies on the accurate execution and review of verification commands. It does not automatically fix issues but requires manual output checking to ensure work completion claims are honest and evidence-based.