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 planning of how a change will be verified, so every claim has a concrete evidence path before implementation begins. ## 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 Affordances: Guides creation of minimal capabilities that make relevant state controllable, observable, repeatable, and diagnosable when existing surfaces are insufficient. - Verification Budgeting: Assigns one owner per distinct claim and selects the minimum non-duplicative evidence covering claims and important boundaries. - Use Case: Before refactoring a payment retry flow, use this Skill to define the exact claims (e.g., no duplicate charges), choose how to observe them, and decide what test support is needed before writing any code. ## Quick Start Ask the agent to build a verification plan for the upcoming feature or bug fix, framing the claim and evidence path before any implementation starts.
