verification-before-completion

To verify task completion, identify the appropriate test command, execute it fresh, read the output, and confirm a successful exit code before making any success claim. This enforces evidence-based status updates and prevents false assertions.

A verification gate is a step-by-step process requiring fresh command execution and output confirmation before declaring any task complete. It enforces rigorous honesty by demanding evidence reporting for testing, linting, building, and code reviews.

Prevent false success claims by requiring fresh command execution, exit-code checks, and evidence reporting before any status update. This process highlights red flags and stops rationalization shortcuts during development cycles.

Yes, you can use this verification process for CI pipelines, commits, PRs, and handoffs. It guarantees evidence-based status updates by requiring developers and reviewers to run commands and confirm output before declaring success.

Manual checks are limited by rationalization and shortcuts, allowing false assertions. A rigorous verification gate stops these red flags by requiring fresh command execution, strict exit-code checks, and explicit evidence reporting before completion.

The best way to enforce honest status updates is applying a verification gate that requires running commands, checking exit codes, and reporting evidence before claiming completion. This prevents false assertions during PRs and handoffs.