What problem does it solve? Design documents, specs, RFCs, ADRs, and plans often get approved with hidden gaps — unstated assumptions, misleading names, missing failure handling, or claims that do not match the actual code — which surface late or in production. This Skill performs an adversarial pre-approval review that finds those gaps before sign-off. ## Core Features & Use Cases - Nine-category gap rubric: Hunts bootstrap/ownership, naming honesty, scale, hidden assumptions, consistency-with-shipped-code, idempotency/failure, security, necessity, and completeness gaps, plus a plan lens (task granularity, dependency DAG, spec coverage, exit-criteria testability). - Codebase verification: Confirms every claim about existing behavior against the real code with file:line citations, marking unconfirmable items as unverified rather than fabricating findings. - Severity-ranked verdict: Produces blocker/important/minor findings with concrete fixes and a ready-for-approval or has-blockers recommendation, without ever editing the document or approving it. - Use Case: Before approving an auth-v2 spec, run the review to catch that the design assumes a token table the codebase never creates, cited at the exact file and line. ## Quick Start Use design-review on docs/specs/auth-v2.md before I approve it and list any blockers.
