What problem does it solve? When a task is nearly done, it is easy to over-engineer: adding polish, unrelated tests, or scope creep instead of simply proving the work meets its acceptance conditions. This Skill enforces disciplined, validation-only behavior so verification stays minimal and honest. ## Core Features & Use Cases - Minimal Proof Sets: Translates acceptance conditions into the smallest sufficient set of checks, reusing still-current results when repository state matches. - Precise Result Reporting: Distinguishes pass, fail, unavailable, and blocked states exactly, and reports commands, results, and unresolved risks. - Scope Discipline: Runs focused checks before wider gates, avoids editing product code unless fixes are requested, and stops immediately once acceptance proof is complete. - Use Case: After implementing a bug fix, ask the agent to verify the fix against the ticket's acceptance criteria. It runs only the relevant tests, reports the outcome, and stops without refactoring nearby code. ## Quick Start Use the verify-and-stop skill to check that the current changes meet the acceptance criteria in the ticket and report the results without making further edits.