What problem does it solve?
Engineers often claim work is complete based on weak or stale evidence, such as a passing compile check or a green exit code that never exercised the intended behavior. This Skill enforces a verification discipline that ties every requirement to current, direct proof before anything is declared done.
Core Features & Use Cases
- Evidence Matrix: Records each requirement alongside its direct evidence, status (proven, failed, blocked, or unverified), and the next useful check.
- Smallest Sufficient Check Selection: Orders verification from diff inspection through focused tests, integration checks, and manual smoke evidence, avoiding unnecessary full-gate runs.
- Completion Audit: Re-reads the original request, enumerates required artifacts and gates, and inspects authoritative state before closing a phase or task.
- Use Case: After fixing a Rust bug, use this Skill to confirm the focused test actually exercised the changed path, separate product failures from environment failures, and state exactly what was proven versus what remains unverified.
Quick Start
Ask the agent to prove whether this phase is actually complete by auditing the implementation against every requirement.