verification-before-completion

To enforce evidence before claims in a CI/CD pipeline, require independent execution of verification commands to confirm actual state before allowing task status updates. This prevents false positives by stopping the propagation of unverified code states.

Mandatory verification for code commits and pull requests is a strict policy requiring developers to run relevant test suites and confirm zero failures in fresh output before claiming work is complete. It ensures all success assertions are backed by evidence.

To prevent false positives when updating task status in agile development, mandate fresh execution of verification commands to confirm the actual state before making positive claims. This stops premature assertions that bugs are fixed or tests are passing.

Yes, this verification policy works without external dependencies. It enforces a strict evidence-first workflow natively by requiring independent execution of commands to confirm actual state before any positive claims are made about work status.

The best way to verify tests passing before claiming work is complete is running the relevant test suite and confirming zero failures in the output. You must then state the success with evidence, ensuring no unverified code is shipped.