superpowers-verification-before-completion

To enforce verification before declaring a pull request complete, run a defined verification command suite, review the full output, and cite the fresh evidence to satisfy your completion claim. This prevents false positives during code reviews.

Claiming task completion without fresh evidence causes issues because it prevents false positives during task handoffs. Running verification commands and collecting actual output ensures outcomes are backed by proof rather than assumptions.

The best way to structure a code review workflow to prevent false completions is enforcing a repeatable process where developers run verification commands, review outputs, and cite evidence before reporting completion status or merging changes.

Yes, you can use this structured verification workflow for task handoffs. It ensures developers collect and provide fresh evidence by running defined verification commands before reporting completion status to the receiving team.

Yes, the verification process works without external dependencies, but it requires a defined verification command suite to exist. You must run these commands and review their full output to cite results for completion claims.