What problem does it solve? Writing a software detailed design (SDD) chapter from a layered Software Requirements Specification is error-prone: entries get derived from the wrong requirement layer, descriptions merely restate requirements instead of explaining how to implement them, and coverage gaps or numbering errors slip through review. This Skill enforces a disciplined derivation workflow so every design entry traces to an implementation requirement and passes automated validation. ## Core Features & Use Cases - Layered derivation rules: Reads all three SRS layers (user/development/implementation requirements) but derives design entries only from implementation requirements, flagging uncovered performance/capacity requirements as coverage risks. - Phased delivery gates: Produces a 14-field requirement analysis list and a 7-field requirement-to-design mapping table for user confirmation before writing formal four-field design entries (ID, name, description, source). - Automated validation scripts: Ships Python scripts that check ID continuity, four-field completeness, source-requirement legality, full implementation-requirement coverage, constraint-copying similarity, and format compliance. - Use Case: Given a GJB 438B-style layered SRS for a multi-tool resource editor, generate the "5 Detailed Design" chapter with 60+ self-contained SD entries, a mapping table proving 91/91 implementation-requirement coverage, and pass all validation scripts before delivery. ## Quick Start Generate the detailed design chapter from my layered SRS file, deriving design entries only from implementation requirements and validating coverage with the included scripts.
