verification-before-completion

To verify code completion before committing, you must execute verification commands like running your test suite and confirm their output passes. This evidence-based verification prevents shipping broken code by requiring actual proof that all checks are passed.

Claiming work completion prematurely causes software quality issues because it bypasses final checks, allowing broken code to be shipped. Requiring evidence from verification commands ensures claims are backed by actual test suite results before finalizing development.

Evidence-based verification in software development is the process of requiring execution of verification commands and confirming their output before any work completion claims are made. It ensures software quality by backing success claims with actual test results.

Yes, you can use this verification process for code review and test suite validation. It is applicable to any scenario where work completion is claimed before final checks, specifically running test suites to verify all tests pass for software quality assurance.

To ensure work integrity, run the 'verify-work' command before committing to execute your test suite and code quality checks. This requires the verification commands to run successfully and provide evidence of their output before you can claim completion.

The limitation of evidence-based work verification is that it requires actual execution of verification commands and confirmation of their output. It cannot validate completion claims if the appropriate test suite or code quality verification commands are not defined or cannot be executed.