juliusbrussee/verify-and-stopv1.0

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.

v1.0Latest

New~165Updated Aug 17, 2026

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.

Files2

2 files · 1.6 KB

Select a file to preview

Overall Score

68/100

Grade

Adequate

Safety

Quality

Clarity

Completeness

Summary

This skill directs agents to validate that existing work meets acceptance conditions without expanding scope, adding polish, or modifying code. It emphasizes focused verification—reusing current results, running targeted checks, and stopping immediately once acceptance proof is complete.

Detected Capabilities

code analysiscommand executionresult reporting

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

validate acceptance criteriaprove completiongate checkstop after proofavoid scope creep

Use Cases

validate acceptance criteria against code
run focused gate checks before wider test suites
distinguish pass/fail/blocked status exactly
confirm completion without scope creep
prove work meets conditions without adding polish

Quality Notes

Clear scope boundaries—explicitly forbids product code edits and scope expansion
Concise and actionable instructions with specific constraints
Provides four distinct outcome states (pass/fail/unavailable/blocked)
Missing implementation details: no concrete examples of acceptance conditions, verification patterns, or command structure
No guidance on how to reuse cached results or detect repository state changes
Limited explanation of what 'focused checks' means in practice or how to prioritize verification
No error handling guidance for edge cases (missing results, conflicting outcomes, ambiguous states)

Model: claude-haiku-4-5-20251001Analyzed: Aug 17, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use juliusbrussee/verify-and-stop in your dev environment — a Developer account adds skills to your library and syncs them via the SkillRepo CLI.

Start a Developer trial