verification-before-completion

Prevent premature completion claims by enforcing a stepwise verification workflow that requires fresh command output evidence before any success assertion. You identify the proving command, run it, review the output, and validate results before acknowledging task completion.

Generate audit-friendly evidence for code review by running the confirming verification command and capturing its full output. This creates an auditable trail stored with the ticket or PR, proving tests or builds passed before claiming completion.

Enforce verification before commits or pull requests by applying a formal stepwise process that requires verifiable command output. You must identify and run the proving command, then validate the results to meet strict quality and honesty requirements before status updates.

Yes, you can use this verification workflow for fixes across development tasks where tests, builds, or code changes must be backed by verifiable command output. It applies broadly to any task requiring strict confirmation before completion.

Task completion claims fail without fresh verification evidence because the workflow strictly prohibits success assertions without recent command output. This requirement ensures quality and honesty by demanding an auditable trail of validated results before acknowledgment.

Limitations of enforcing fresh verification before status updates include the rigid requirement to run a confirming command and manually validate its output for every task. This strict stepwise process may add overhead to rapid development cycles where instant completion is expected.