What problem does it solve? It closes the final gap in a spec-driven development workflow by objectively comparing the implemented repository state against the original SPEC.md requirements, preventing unverified or drifting code from being marked complete. ## Core Features & Use Cases - Spec-to-Code Verification: Compares every SPEC.md requirement item against the actual implementation, using project checks and direct code inspection as evidence. - Verdict-Based State Management: Writes pass, no-pass, or blocked verdicts into STATE.json, completing the workstream on pass or routing actionable gaps back to the spec phase. - Structured Findings: Records hard blocks, soft findings, and observations in VERIFY.md following a strict schema, with enough detail for the spec phase to rewrite requirements. - Use Case: After all planned tasks in a workstream are marked done, run this skill to confirm the implementation satisfies every requirement before closing the workstream. ## Quick Start Run the verify phase on the current workstream to check the implementation against SPEC.md and report whether it passes.
