What problem does it solve? Non-trivial code changes often ship with unverified assumptions because teams default to familiar tests instead of asking how the system itself can prove a claim. This Skill structures the planning of a credible, project-specific evidence path before implementation begins. ## Core Features & Use Cases - Claim Framing: States the behavior that must become true, its meaningful uncertainty, and its important failure modes before any code changes. - Evidence Path Design: Derives verification routes from the system's controllable inputs, observable effects, state transitions, invariants, and boundaries, with alternatives and a verification budget. - Verification Affordances: Defines the smallest capability that makes relevant state controllable, observable, repeatable, and diagnosable when existing surfaces are too indirect. - Use Case: Before refactoring a cross-system payment flow, use this Skill to frame the behavioral claim, choose a proportionate evidence path, budget verification across distinct claims, and close the loop by interpreting evidence after implementation. ## Quick Start Ask the agent to build a verification plan for the upcoming feature or refactor before writing any implementation code.
