verification-before-completion

To verify software work before claiming completion, execute validation commands like tests or builds, review their actual outputs, and confirm the results match your status assertions before reporting success.

Evidence-based reporting in software engineering means ensuring tests, builds, fixes, and requirements are confirmed through actual validation command outputs before reporting the work as finished or successful.

Prevent unsupported completion claims in development workflows by applying verification gatekeeping, which requires identifying and running proof commands to confirm results before making status assertions.

Yes, you need to run validation commands before creating a pull request to ensure the reported implementation state matches verified results and prevent inaccurate completion claims.

Yes, you can use verification checks for delegated agent tasks by requiring fresh verification evidence and reviewing outputs to confirm successful results before reporting the delegated work as complete.

The best way to confirm a software fix is actually successful is requiring fresh verification evidence by executing validation commands, reviewing outputs, and confirming results before making status assertions.