verification-before-completion

To enforce verification before completion, execute required verification commands and ensure all checks pass before declaring success. This approach requires concrete test results, lint outputs, and build logs to validate task completion.

Evidence-based success in quality assurance means backing work claims with fresh evidence like test results and build logs. It enforces explicit verification steps before commits or releases to prevent premature or dishonest completion claims.

To prevent premature completion claims, run a full verification sweep by executing required commands and reading their outputs. You must identify, run, read, and verify all checks before committing, creating PRs, or releasing features.

Yes, this gatekeeping approach applies to any development task before committing, creating PRs, or releasing features. It provides a clear gate function to identify, run, read, verify, and only then claim completion status.

You need fresh evidence and failure reporting to prevent faulty releases and false positives. Claiming work is complete without verification leads to dishonesty, so enforcing explicit verification steps ensures all checks pass before customer-facing claims.

The limitation of relying on verification commands is that it strictly enforces evidence-based completion. If verification steps fail, it requires explicit failure reporting and prevents any completion claims until concrete test results and build logs validate success.