superpowers-verification-before-completion

To prevent premature completion claims, enforce a verification gate that requires running verification commands and evaluating outputs before marking any pull request done. This ensures success statements are gated on confirmed evidence rather than assumptions.

Evidence-based verification is a gatekeeping process that requires fresh verification outputs to prove outcomes before declaring tasks complete. It enforces accountability by ensuring software development claims are backed by confirmed results.

You can enforce a quality-assurance gate by implementing a workflow that requires running verification steps and evaluating their outputs before approving releases or handoffs. Success is gated strictly on confirmed verification results.

Yes, this verification gate applies to sprint handoffs, task completions, and code reviews. It requires running fresh verification commands and gating success statements on confirmed results to ensure proven outcomes.

The best way to prove task outcomes is to implement a gate workflow that runs verification commands, evaluates the outputs, and gates any completion claims on those confirmed results. This prevents unverified success statements.

Requiring verification before declaring a task done prevents unverified claims and ensures integrity across teams. By gating completion statements on fresh verification outputs, you enforce accountability and prove outcomes with evidence.