Summary

A minimal validation-gate skill that directs agents to prove acceptance criteria are met without expanding scope. It emphasizes reusing existing results, running focused checks, and stopping immediately when criteria pass — avoiding additional polish, cleanup, or unrelated work.

Detected Capabilities

Trigger Keywords

Phrases that agents use to match this skill to user intent.

Use Cases

• Validate that code meets documented acceptance criteria before merging or deployment
• Run a focused set of acceptance tests without adding new tests or polish
• Distinguish between passing, failing, unavailable, and blocked status for verification gates
• Reuse existing test results when repository state hasn't changed
• Confirm completion of a feature or fix without scope creep

Quality Notes

• Strengths: Clear problem scope (validation only, no scope expansion). Explicit constraints prevent undesired agent behavior (no code editing unless part of criteria, no polish/cleanup). Concise and actionable framing.
• Weaknesses: Extremely minimal content — no concrete examples of acceptance conditions, verification commands, or pass/fail criteria. No guidance on what 'still-current results' means or how to detect repository state changes. No examples of the four outcome states (pass, fail, unavailable, blocked). Missing error-handling guidance for unexpected test failures or missing prerequisites.
• Completeness gap: The skill lacks concrete implementation details. An agent needs examples of: (1) how to detect repository state, (2) representative acceptance criteria and matching proof commands, (3) how to report the four outcome states, (4) when to escalate or request clarification.