What problem does it solve? AI-driven development often drifts from the plan: tasks get marked done without evidence, scope creeps, and gaps go unnoticed. This Skill acts as a per-task verification gate in the SPAE workflow, comparing the active task's implementation against its declared Intent, Acceptance, and Verification criteria before allowing progress. ## Core Features & Use Cases - Evidence-based gating: Runs the task's verification steps and project checks, then labels every finding as either a blocking Gap or a non-blocking Observation. - State machine routing: Writes STATE.json transitions—gaps route to /fix with a structured FIX.md, clear tasks advance the cursor to /build, and a clear final task routes to /verify. - Scope discipline: Enforces KISS/YAGNI by flagging speculative abstraction, unrequested complexity, and self-introduced cleanup violations grounded in the task's own git diff. - Use Case: After a build agent implements task T-002 of a workstream, run the check phase to confirm every acceptance criterion with reproducible evidence; if a gap exists, FIX.md is written with file:line, expected vs actual, and the workflow routes to /fix automatically. ## Quick Start Run the check phase to verify the active task in .spae/current/PLAN.md against its acceptance criteria and update STATE.json with the verdict.
