What problem does it solve? Code and the documents that specify it drift apart, and finding where requires reading every requirement against every enforcement path — work that exceeds a single context window and produces unreliable verdicts when rushed. This Skill fans the check out so each requirement gets its own evidence-backed verdict. ## Core Features & Use Cases - Per-requirement verdicts: Each requirement is classified as implemented, partial, contradicted, stronger-than-spec, absent, or undecidable, with cited code lines and recorded searches. - Independent refutation: Divergences are sent to agents that did not produce them, so findings survive adversarial re-reading of both code and document before being reported. - Reverse-direction coverage: The report also surfaces behavior the code has that no document mentions, which a document-driven pass cannot find by construction. - Use Case: Point it at a Solidity codebase and its whitepaper to learn which stated guarantees hold, which fail on untested paths, and which constraints exist only in the code. ## Quick Start Run the spec-compliance workflow on your code directory against your specification document, for example by asking to check ./contracts against SPEC.md.
