Menu
Use when verifying acceptance criteria. Binary verdict per criterion. Evidence-based.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when reviewing architecture decisions. C4 model, dependency inversion, hexagonal boundaries.
Use during discuss-slice and plan-slice to stress-test a spec or plan against domain vocabulary before approval.
Use during research-slice to build disposable experiments that answer technical uncertainty.
Use during project:init to scaffold repo-level agent configuration (CLAUDE.md, AGENTS.md, tracker labels).
Use when debugging. 4-phase investigation, root cause, minimal fix.
Use when implementing features/fixes. Iron law: ¬∃ production code without failing test.
| name | acceptance-criteria-validation |
| description | Use when verifying acceptance criteria. Binary verdict per criterion. Evidence-based. |
| version | 1.0.0 |
| tags | ["process","validation"] |
∀ verification ∧ acceptance testing. ∀ spec validation.
∀ criterion: verdict is PASS ∨ FAIL. ¬"partially met". ¬"close enough". Binary.
∀ acceptance criterion ∈ SPEC.md:
| AC | Verdict | Evidence |
|---|---|---|
| AC1: User can login | PASS | npm test -- auth.spec.ts -> 4/4 passing |
| AC2: Rate limit at 100/min | FAIL | No rate limit test ∃ |
∀ criterion must be:
