Vibe Acceptance Gate
Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
Install
$ agentstack add skill-ash1794-vibe-engineering-acceptance-gate ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ash1794-vibe-engineering-acceptance-gate) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
vibe-acceptance-gate
Don't claim "done" until you've checked against the criteria that define "done."
When to Use This Skill
- After completing a task that has acceptance criteria
- Before marking an issue/ticket as resolved
- When the user asks "is this done?"
- After implementing a spec with defined requirements
When NOT to Use This Skill
- Exploratory work with no defined criteria
- Research tasks (use
vibe-reflect-and-compoundinstead) - When criteria haven't been defined yet (define them first)
Steps
- Find the criteria — Look in:
- Issue/ticket description (MUST/SHOULD requirements)
- Spec document (acceptance criteria section)
- Task description (success conditions)
- User's original request (implicit criteria)
- Validate each criterion — For each one:
- Run the relevant test, command, or check
- Record PASS (met), FAIL (not met), or PARTIAL (partially met)
- Capture evidence (test output, code reference)
- Report results:
| # | Criterion | Status | Evidence | |---|-----------|--------|----------| | 1 | [criterion text] | PASS/FAIL/PARTIAL | [evidence] |
- Gate decision:
- All PASS → Task complete
- Any FAIL on MUST criteria → Task NOT complete, list remaining work
- PARTIAL only → Report what's missing, ask user if acceptable
Output Format
Acceptance Gate: [Task Name]
Result: PASS / FAIL / PARTIAL Criteria Met: X/Y (Z%)
| # | Criterion | Status | Evidence | |---|-----------|--------|----------| | 1 | ... | ✓/✗/◐ | ... |
Remaining Work (if FAIL)
- [What needs to be done]
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ash1794
- Source: ash1794/vibe-engineering
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.