obra/superpowers@verification-before-completion

You enforce verification evidence by applying a gate workflow that identifies the proving command, runs it fully, reads the outputs, and verifies the results before confirming any pull request completion.

A verification gate in software engineering governance is a checkpoint that requires fresh, verifiable proof of success—such as passing test outputs—before allowing a code change, deployment, or task handoff to be marked complete.

To stop premature completion claims during code review and task handoffs, require the submitter to run the full verification sequence and attach the output evidence before declaring the work done.

Yes, this evidence-based verification approach works for deployments and task handoffs, applying the same identify, run, read, and verify gate pattern to prevent unverified conclusions across all development workflows.

The best way to verify code changes before marking a task as done is to implement a governance pattern that identifies a proving command, executes it, and reads the output to ensure evidence-backed progress and quality assurance.