harness:verification-before-completion

What problem does it solve?

Prevents premature or dishonest completion claims by requiring fresh verification evidence before you declare work complete, passing, fixed, or ready.

Core Features & Use Cases

• Evidence-first completion gate: Forces you to identify the exact command that proves completion, run the full verification, and only then communicate success.
• Gap-aware verification reporting: Blocks completion when any acceptance criterion is unsatisfied and reports the specific gap instead of general confidence.
• Layer and architecture guardrails: Ensures verification includes required architecture-layer checks and flags reverse-direction dependency violations.
• Use case: Before merging or archiving a change that claims rate-limit behavior, run the required verification and report whether each acceptance criterion (for example Retry-After header) is actually satisfied.

Quick Start

Ask your AI to run verification for the current building feature and only report “verified” with explicit evidence for every acceptance criterion.