What problem does it solve? Detailed design documents drift from their SRS requirements: entries lose traceability, contain unverifiable vague wording, miss boundary and exception cases, and use inconsistent terminology. This Skill audits SD-* design entries against SRS implementation requirements so every requirement is covered exactly once and every design statement is testable. ## Core Features & Use Cases - Five-dimension audit: Checks verifiability, input/output explicitness, boundary and exception coverage, terminology consistency, and HOW-depth balance, then outputs a problem list with full before/after entry text and waits for explicit approval before editing. - Read-only review modes: Runs requirement-coverage review (six-section report with eight checks), horizontal-consistency review (10 standards), and final delivery gate checks (13 rules) without modifying any files. - Feasibility and gap assessment: Evaluates whether developers can build deliverable software from the document, classifying gaps as document-fixable, external dependencies, or items needing technical spikes. - Use Case: Given an SRS with REQ-F implementation requirements and a detailed design document with SD-1 through SD-61 entries, run the audit to verify zero missing or extra requirement references, symmetric failure-cleanup behavior across sibling entries, and consistent module naming, then apply approved fixes in batches verified by the included Python script. ## Quick Start Ask the agent to audit the detailed design document's SD entries against the SRS implementation requirements for traceability, verifiability, and boundary coverage.
