verification-discipline

What problem does it solve?

It prevents teams from claiming completion without proof by enforcing evidence-first verification, risk-proportional testing, and explicit reporting of what was or was not verified.

Core Features & Use Cases

• Evidence-first verification planning: picks the smallest relevant command first, then expands verification based on change risk.
• Failure-loop debugging: parses the exact error, forms one root-cause hypothesis, applies one focused fix, and reruns the smallest failing check.
• Unverified disclosure: if verification can’t run, it states exactly what remains unverified and why.
• Use case: when you change dependencies, code, or CLI/install behavior and need audit-proof confidence that the change works and doesn’t introduce regressions.

Quick Start

Ask the assistant: “Apply verification-discipline to my change by listing the smallest safe verification commands, expanding checks based on risk, and producing a final report that includes evidence and any explicitly unverified items.”