What problem does it solve? When a feature's Technical Requirements Document (TRD) lists many use cases, it is hard to know which ones are actually implemented in code and which exist only on paper. This Skill automates that comparison so teams can see implementation gaps without manually re-reading the TRD and grepping class by class. ## Core Features & Use Cases - Automated TRD-to-code comparison: Parses section 6 ("Casos de uso") of specs/<slug>/trd.md and searches src/ and frontend/ for each use case class name, producing a table of use case | acceptance criterion | implemented (yes/no) | evidence file. - Cross-platform scripts: Ships both a Bash script and a PowerShell script, with configurable search paths for projects using non-standard folder conventions (e.g., Laravel's src/app/Application/UseCases/ or monorepos). - Honest gap signaling: Flags that a "NÃO" result is a text-search heuristic, not proof of missing implementation, and instructs manual confirmation before blocking decisions. - Use Case: Before a release review, run the report on a feature slug to instantly see which of the 12 planned use cases have real code behind them and which are still only designed in the TRD. ## Quick Start Ask the assistant to run the gap report for a feature, for example: "Run /sdd-gap-report for the checkout feature and tell me which use cases from the TRD are not implemented yet."
