← LeaderboardThe Skill Leaderboard

verify-and-stop

Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.

Published by JuliusBrussee ↗JuliusBrussee/caveman

Try your first task

verify-and-stop

Start a fresh conversation. Replace the highlighted placeholders.

Use verify-and-stop to verify whether [project or change] meets [acceptance conditions] using the smallest sufficient proof set; report commands, results, and unresolved risk, without expanding scope or editing product code.

Required inputs

[project or change]
[acceptance conditions]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: verify-and-stopdescription: Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile proof.

Verify and stop

Translate acceptance conditions into smallest sufficient proof set.

Reuse still-current results with matching repository state.
Run focused checks before wider gates.
Distinguish pass, fail, unavailable, and blocked exactly.
Do not edit product code unless verification request includes fixes.
Do not add polish, cleanup, or unrelated tests after criteria pass.

Stop immediately when acceptance proof is complete. Report commands, results, and unresolved risk only.