What problem does it solve? Project documentation drifts from the code it describes: dead file references, symbols that exist only in comments, and promises in specs that the code never fulfills. This Skill provides a structured, five-pass review procedure that audits an entire domain's binding between specification statements and the code they point to. ## Core Features & Use Cases - Five ordered passes: three machine-executed checks (dead addresses, comment-only anchors, symbols not declared in the named file) followed by two manual reading passes (promise-versus-code verification, and lookup of numbers, refusal codes, and glossary keys). - Hit triage discipline: treats each pass's output as a reading queue rather than a defect list, recording both the raw hit count and the confirmed divergence count. - Layer-aware expectations: recognizes that false-positive rates differ between procedural layers and component/service layers, so only the pass order carries over between domains. - Use Case: After a large refactor moves code out of a documented domain, run the sweep to find every spec statement whose referenced file or symbol no longer exists, then read the flagged lines to confirm real divergences. ## Quick Start Run the spec-driven sweep over the authentication domain to audit every spec statement against the code it references.
