verification-before-completion

To enforce evidence verification before a commit, mandate specific verification command execution and evidence checking. This reduces false completion claims by requiring strict proof of passing tests before any work outcome is considered complete.

Verification before completion is a quality assurance process validating work claim integrity prior to pushing changes. It requires developers to execute verification commands and provide evidence that code changes pass necessary checks.

You verify code changes by running a dedicated verification command with the specific task identifier. This generates an evidence summary in the output that proves the task is fixed or passing before you push the PR.

Yes, you can track work integrity by enforcing clear and honest tracking of every task. This includes assigning specific severity and confidence levels to ensure high integrity standards across the development team.

Yes, enforcing strict evidence before commit works independently without external dependencies. It operates as a standalone discipline to mandate verification steps and evidence checking directly within your existing development workflow.

Relying on manual verification lacks consistent enforcement of evidence before claim philosophies. Without a structured process requiring explicit command execution, development teams risk false claims and reduced trust in work outcomes.