verification-before-completion

You can enforce verification by running predefined verification commands and comparing the output evidence to your completion claims before asserting work status. This structured process ensures claims are backed by evidence rather than assumptions.

Evidence-based work status verification is a process that requires executing validation commands and checking their output to prove task completion. It prevents premature completion claims by demanding manual comparison of output against stated assertions.

To verify project completion claims, execute predefined verification commands and manually check the output for issues. Only assert task completion after confirming the output evidence matches the original claim.

Yes, this structured verification process is applicable to software development, project management, and quality assurance workflows. It guides users through validating completion claims regardless of the specific project context.

The best way to prevent premature completion claims is to enforce a structured verification process. This involves executing verification commands, checking the output for issues, and only claiming success after verifying the evidence matches the claim.

You should require manual execution of verification commands to ensure evidence matches your completion claims. This prevents premature assertions by forcing a structured comparison of actual command output against expected work status.