verification-before-completion

To verify code changes before completion, run the exact verification commands like tests or builds, inspect their full outputs and exit codes, and attach the evidence before declaring the task successful.

A verification gate is a stepwise protocol requiring you to run a fresh proving command, read its full output and exit code, and only then state success, preventing premature completion claims in your developer workflow.

Validate agent-reported success by checking VCS diffs and independently running the exact verification commands to produce fresh execution evidence, ensuring you do not rely on unproven agent assertions of task completion.

You need to enforce pre-commit and pre-PR verification when about to commit, create a pull request, finish a task, or move to the next step, ensuring your tests, builds, and linters are genuinely passing.

Yes, you can use this verification protocol for local TDD and code quality checks by applying it whenever you finish a step, requiring fresh execution of linters and test suites with attached output evidence before any success statements.