What problem does it solve? Large SRS documents accumulate dead requirements, stale cross-references, concept confusion, scope leaks, and silently rotted indexes after edits. This Skill provides a systematic audit methodology that finds these defects before the document drives design and implementation. ## Core Features & Use Cases - 12 Structured Audit Passes: Detect dead requirements, stale cross-references, terminology drift, implementation-detail leaks, scope violations, missing behaviors, and framework coverage gaps. - Post-Edit Consistency Sync (Pass J): After any add/delete/renumber, re-verify section indexes, statistics tables, numbering rules, deferred-requirements appendix, and change logs. - SRS-to-Code Coverage Analysis (Pass K): Compare requirements against actual source code across C#, TypeScript, and .razor layers, or audit an existing coverage report for accuracy. - Use Case: After bulk-renumbering requirements in a 4700-line SRS, run the post-edit consistency check to catch broken indexes, stale statistics, and hardcoded ID ranges before handoff. ## Quick Start Review docs/SRS.md for dead requirements, terminology confusion, scope leaks, missing acceptance criteria, and stale cross-references, reporting findings without editing the document.