From guided-dev
Verify each acceptance criterion against the implementation with concrete evidence. Use when checking requirements, verifying implementation, or confirming acceptance criteria are met.
How this skill is triggered — by the user, by Claude, or both
Slash command
/guided-dev:verifyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematically checks each acceptance criterion from the intake phase against the actual implementation. Produces a pass/fail checklist with concrete evidence for each criterion, and identifies what needs fixing before the task can be considered complete.
Systematically checks each acceptance criterion from the intake phase against the actual implementation. Produces a pass/fail checklist with concrete evidence for each criterion, and identifies what needs fixing before the task can be considered complete.
Recall the acceptance criteria from the intake summary. List them explicitly before beginning verification.
For each acceptance criterion, perform a concrete check:
Read to examine the relevant code. Verify the logic matches the requirement. Trace the code path end-to-end where possible.Bash to run them and confirm they pass.browser_take_screenshot and save to docs/guided-dev/verify-screenshot-NN.png (NN = zero-padded criterion number)Bash with curl to hit endpoints and verify response shapes, status codes, and payloads. Otherwise, check route definitions, handlers, and test results.Output in this format:
## Acceptance Criteria Verification
| # | Criterion | Status | Evidence |
|---|-----------|--------|----------|
| 1 | <criterion text> | [PASS] or [FAIL] | <specific evidence — file:line, test result, Playwright screenshot path, or observation> |
| 2 | <criterion text> | [PASS] or [FAIL] | <specific evidence> |
| ... | | | |
### Summary
- **Passed:** N of M
- **Failed:** N of M
If any criteria fail:
### Failed Criteria — Fixes Needed
1. **<Criterion>** — [FAIL]
- **What's wrong:** <specific description of the gap>
- **Suggested fix:** <concrete steps to fix>
- **Files to change:** `<path>`, `<path>`
Would you like me to fix these issues before proceeding?
If the user agrees, fix each issue and re-verify the failed criteria.
Once all criteria pass (or the user explicitly accepts the remaining failures):
All acceptance criteria verified. Ready to proceed to quality review.
npx claudepluginhub kevnord/claude-plugins --plugin guided-devVerifies feature completion by requiring automated tests that prove functionality works. Enforces phase gates and spec alignment before acceptance.
Use when marking a task as complete, finishing a feature, or claiming a bug is fixed. Ensures functional resolution is verified with evidence before closing.
Verifies implementation against a spec with evidence-based checks and three independent self-consistency passes. Ensures every requirement is backed by verbatim evidence before merge.