verify-and-stop
juliusbrussee/caveman
Prove existing work meets acceptance conditions without expanding scope.
What is verify-and-stop?
Verify-and-stop translates acceptance conditions into the smallest sufficient proof set, enabling validation-only tasks and completion checks. Use it when you need focused gate runs and last-mile proof without scope creep or unnecessary polish.
- Reuse still-current results when repository state matches
- Run focused checks before wider gates
- Distinguish pass, fail, unavailable, and blocked outcomes exactly
- Avoid editing product code unless verification request includes fixes
- Stop immediately when acceptance proof is complete
How to install verify-and-stop
npx skills add https://github.com/juliusbrussee/caveman --skill verify-and-stopHow to use verify-and-stop
- 1.Identify the acceptance conditions that must be proven
- 2.Determine the smallest sufficient set of checks needed
- 3.Run focused verification commands against the current codebase
- 4.Report results with commands executed and any unresolved risks
- 5.Stop immediately upon completion—do not add polish or unrelated tests
Use cases
- Validate that existing work meets specific acceptance criteria before merging
- Run focused test gates on a feature without expanding scope
- Perform last-mile proof of completion for a task
- Check if prior results are still valid given current repository state
- Gate a deployment by verifying only essential acceptance conditions
- QA engineers validating completion criteria
- Developers doing final verification before merge
- Project leads confirming task completion
- Teams using gate-based deployment workflows
verify-and-stop FAQ
No. Do not edit product code unless the verification request explicitly includes fixes.
Stop immediately. Report the commands run, results obtained, and any unresolved risk. Do not add polish, cleanup, or unrelated tests.
Yes, if the repository state still matches. Reuse still-current results to avoid redundant work.
Distinguish pass, fail, unavailable, and blocked outcomes exactly in your report.
Full instructions (SKILL.md)
Source of truth, from juliusbrussee/caveman.
name: verify-and-stop description: 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.
Related skills
More from juliusbrussee/caveman and the wider catalog.
cavecrew
Three compressed-output subagents for code location, surgical edits, and diff review—save context tokens across delegations.
caveman
Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy.
caveman-commit
Write terse, Conventional Commits messages focused on intent, not description.
caveman-compress
Compress memory files into caveman-speak to reduce input tokens while keeping readable backups.
context-canary
Install a per-turn canary signal to detect silent context degradation and trigger recovery when it fails.
fuck-slop
Strip AI writing fingerprints and rewrite text into its target register—academic, tweet, email, blog, anything.