What problem does it solve? Non-trivial code changes often ship without a credible way to prove they work, leaving teams guessing whether a feature, bug fix, or refactor actually behaves as claimed. This Skill structures the upfront thinking needed to decide how a specific change can be verified before any code is written. ## Core Features & Use Cases - Evidence Path Design: Frames the claim being made, then derives project-specific ways to establish, limit, or refute it using the system's inputs, outputs, state transitions, and boundaries. - Verification Budgeting: Assigns one owner per distinct claim and selects the minimum non-duplicative evidence that covers all claims and important boundaries. - Verification Affordances: Defines the smallest capability (test hooks, resettable state, diagnostic surfaces) that makes the relevant behavior controllable, observable, and repeatable when the existing system is too indirect. - Use Case: Before refactoring a payment retry mechanism, use this Skill to map out which claims must hold (idempotency, ordering, failure recovery), what evidence establishes each, and whether a temporary test affordance is needed to observe internal state. ## Quick Start Ask the agent to plan a verification approach for the feature or bug fix you are about to implement, including the claims to prove and the evidence needed for each.
