superpowers-verification-before-completion

To enforce verification before claiming task completion, you must execute a fresh verification sequence and validate exit codes. This ensures that status claims in code reviews and PRs are substantiated with actual outputs and evidence rather than premature assertions.

Evidence-driven completion governance is the discipline of requiring verification command outputs and exit codes before making any success claim. It ensures traceability and honesty in work statuses by attaching parsed verification results to substantiate PR and release alignment.

You verify PR and release checks by running the full verification workflow, parsing command outputs, and validating exit codes. This guarantees that completion claims reflect verified results, providing evidence-rich reporting for merges and releases.

Claiming task completion without verification causes premature assertions that lack traceability. By enforcing a verification gate that requires executing commands and validating exit codes, you ensure that success claims honestly reflect actual execution results.

Yes, you can apply verification gates to release checks without external dependencies. The enforcement relies on executing your existing verification commands, parsing their outputs, and validating exit codes to substantiate completion claims with evidence.