verification-before-completion

To enforce tests before claiming code completion, you need a strict verification protocol that requires executing specific commands and checking their exit codes and output before making any success assertions. This prevents premature claims of work completion by demanding evidence before assertions.

The evidence before assertions principle in software development requires concrete command output and exit codes as proof of success before committing code or updating task status, preventing assumptions or previous states from substituting actual test suite and linter verification results.

To prevent premature bug fix claims during code review, identify and run the command that proves the claim, read its full output, verify it confirms the expected results, and only then make the claim with evidence. This ensures mandatory verification of all task completion steps.

Yes, you can use automated verification for task management status updates by applying a mandatory protocol that checks command output and exit codes before any status update is made. This applies to all stages of development where assertions of completion are made.

Yes, verification before completion works without external testing dependencies because it functions as a process protocol rather than a tool integration. It requires you to identify and execute relevant verification commands, then validate their output and exit codes before making any success claims.

You need to verify command output before committing code because relying on assumptions or previous states risks introducing regressions or broken builds. Mandatory verification of test suites and linters ensures concrete proof of success, preventing costly errors from unverified completion claims.