verification-before-completion

Enforcing verification before completion requires identifying the specific verification command, running it, reviewing the full output, and confirming a successful exit code before asserting any status update. This process ensures claims are backed by fresh evidence.

Premature completion claims occur when a development workflow lacks formal governance requiring fresh verification evidence. Without a mandated step to run verification commands and validate exit codes before status updates, honest and traceable progress cannot be guaranteed.

Validating feature completion involves identifying the appropriate verification command, running it to generate fresh output, and verifying a successful exit code. Only after reviewing these results should you assert completion with supporting evidence in your pull request.

Yes, a formal verification workflow can be applied to coding tasks, feature releases, and any software development work item. It guides you through identifying, running, and validating verification steps to ensure honesty and traceability across all governance processes.

Verifying outputs before a commit requires running the full verification command, reading the complete results, and ensuring the exit code reflects success. You must review this fresh evidence thoroughly before making any completion claim or status assertion.

Formal verification steps are needed in quality assurance whenever a status update, commit, PR, or release is required. They prevent premature completion claims by demanding that you run verification commands and validate fresh evidence before proceeding.