superpowers-verification-before-completion

Evidence-based verification enforces a formal gate requiring running tests and command outputs before marking work done. The workflow uses a stepwise procedure—identify, run, read, verify, and report—to generate fresh evidence for completion claims.

Preventing premature completion claims requires attaching fresh command outputs to the PR or task log. The verification workflow integrates into review and commit workflows, explicitly checking failure modes and evidence before final approval.

A formal verification gate integrates into software development workflows by applying a stepwise procedure during task finalization and code review. It requires running tests and checks, reading outputs, verifying results, and reporting evidence before closing a feature.

Completion verification suits feature closure and stakeholder handoffs by enforcing repeatable test and check workflows. It generates trustworthy evidence through command outputs, ensuring work is not merged or handed off without fresh verification.

Evidence-first task completion identifies explicit failure modes when verification steps detect unverified claims. The workflow prevents deceptive status updates by requiring test execution and command output reading before reporting final results.