verification-before-completion

To verify code claims before opening a pull request, execute the specified verification command and read its output to ensure the result matches the claim. This prevents premature success claims by requiring fresh evidence rather than relying on stale test output.

The best way to prevent premature success claims after a TDD cycle is to apply a verification gate that executes the exact command proving the claim. This ensures the latest code state is reflected by disallowing reliance on stale output before reporting progress.

To enforce a quality gate before committing or merging code, apply a verification step that forces execution of the exact checklist or command proving the claim. It reads the fresh output to confirm the result matches the stated claim before completion.

Yes, verification before completion works for delegated tasks and major fixes. It applies a quality gate that executes the specified verification command, reads the output, and ensures the result matches the code claim before reporting progress or marking the work complete.

Relying on stale test output causes issues because it does not reflect the latest code state, leading to premature success claims. Fresh verification disallows stale output by forcing execution of the exact command that proves the claim before marking work as complete.

You need to run a verification command to confirm a code claim before committing, opening pull requests, merging, or reporting progress after delegated tasks, TDD cycles, or major fixes. This ensures fresh evidence matches the claim before marking work complete.