Radberi-VerificationBeforeCompletion

What problem does it solve?

Prevent dishonest completion claims by enforcing evidence-based verification before any status update, merge, or release. This rule ensures that every assertion is backed by fresh test and verification outputs.

Core Features & Use Cases

• Enforces a stepwise verification gate before claiming completion, including identifying the proving command, running it fresh, reading full outputs, and verifying results.
• Provides clear guidance on red flags and common failure modes to avoid false positives.
• Applicable to software development workflows (PRs, merges, releases) to improve trust and reduce rework.

Quick Start

Run the full verification gate to prove success by identifying the command, executing it freshly, reading the output, verifying the result, and only then asserting the claim.