What problem does it solve? Engineering teams need an independent acceptance gate that decides whether a finished feature specification is complete enough to plan, build, and test from, without the author grading their own work. ## Core Features & Use Cases - 10-Condition Acceptance Gate: Judges a spec against a single-sourced implementability and testability checklist covering traceability, unambiguous behavior, complete I/O and states, edge-case handling, testable acceptance criteria, consistency, feasibility, open questions, NFRs, and delta-scoped amends. - Machine-Parseable Verdict: Emits exactly one line, VERDICT: approve or VERDICT: revise, followed by actionable findings naming the failed condition, location, and concrete fix. - Proportional Review: Collapses conditions a thin feature legitimately does not need (no state table, no NFRs, no changelog on a first draft) to avoid false-revise verdicts. - Use Case: After a producer authors a feature spec for a new checkout flow, run this skill before sprint planning to confirm every behavior is unambiguous, every edge case names its handling, and every acceptance criterion is independently testable. ## Quick Start Review the finished feature spec at docs/specs/checkout-v2.md and emit an approve or revise verdict with actionable findings.
