superpowers-verification-before-completion

To enforce verification before claiming task completion in CI-CD, implement a gatekeeping mechanism that requires fresh evidence by running full verification commands and analyzing exit codes and outputs before reporting the actual state.

Progress validation gatekeeping is a quality assurance process that prevents unverified completion claims by requiring fresh verification evidence, ensuring honesty and reliability when reporting progress for code fixes or PR readiness.

You can prevent silent failures during code fixes and PR readiness checks by implementing a verification gate that prompts for command selection, runs the full verification command, and analyzes exit codes and outputs to confirm success.

Yes, you can use verification evidence gates for quality assurance on any task where assertions of progress or finish are made, including tests, builds, code fixes, and PR readiness, to generate an auditable status.

The best way to verify task progress before merging or releasing is to run the verification command, review the results, and only claim completion if the evidence confirms success, avoiding silent failures through rigorous gatekeeping.

Requiring fresh verification evidence improves quality assurance by enforcing a review gate before success claims are made, preventing unverified completion claims and ensuring reliability when reporting progress or completion.