Verification Before Completion

To verify task completion before creating a pull request, define explicit verification commands, execute them fully, and present fresh output as evidence against a success criterion. This prevents unsupported completion claims and reduces rework by validating results.

Evidence-based reporting in software quality assurance is the practice of validating completion claims by running fresh checks against full command output and exit status. It ensures every claim of task completion is backed by explicit, up-to-date verification evidence.

You need to enforce verification steps for project governance when making completion claims, committing code, or creating PRs. It is required in software development and QA tasks to prevent premature announcements and ensure all claims are validated with fresh evidence.

Yes, this verification approach works without external dependencies. It is a standalone policy that enforces verification by requiring explicit commands to be executed fully within your current environment, interpreting the exit status and output against defined success criteria.

The best way to prevent premature completion claims in software development is to enforce a policy requiring fresh evidence before announcing completion. Run explicit verification commands, check the full output and exit status, and interpret results against a success criterion.

Claiming completion without fresh evidence causes rework because unvalidated claims often hide unresolved issues. By enforcing explicit verification commands and interpreting full output against success criteria, you catch failures early and prevent dishonest or unsupported completion claims.