Choose which proportionate evidence proves a claim and interpret its result, including delayed or ambiguous runs. Writing or pruning tests belongs to the testing skill.
Installs into .claude/skills of the current project.
Are you the author of Verification?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tompassarelli-verification)
---
name: verification
description: >-
Choose which proportionate evidence proves a claim and interpret its result, including delayed or ambiguous runs. Writing or pruning tests belongs to the testing skill.
grounded: 2026-10-09
written: 2026-10-10
---
# Verification
1. Name the stable acceptance claim and the action its result changes.
2. Run the smallest operator-visible journey before deeper component checks.
3. Hold its candidate and verdict-sensitive launcher, environment, TTY and fixture state stable.
4. Reuse passing results until a relevant behavior change invalidates them; run each check once, and once more after a fix.
5. Resolve ambiguous observations and repair the first actual divergence before another expensive run.
6. Reassess at roughly twice the estimate and restart only for observed failure or a supported corrective change.
Read [evidence, pricing and diagnosis](references/notes.md) when choosing checks or diagnosing delayed runs.
