What problem does it solve? When a feature is mid-development, it is hard to know which use cases from the Technical Requirements Document (TRD) are actually implemented in code and which exist only on paper. This Skill automates that comparison so you do not have to reread the TRD and grep for each class name manually. ## 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. - Custom search paths: Accepts extra directory arguments for projects with non-standard layouts (e.g., Laravel's src/app/Application/UseCases/ or monorepos). - Cross-platform scripts: Ships both a Bash script and a PowerShell script producing the same table: use case | acceptance criterion | implemented (yes/no) | evidence file. - Use Case: Before a code review or merge decision, run the report for a feature slug to see which TRD use cases still lack implementation evidence, then confirm any "NÃO" results with a targeted manual check. ## Quick Start Ask the assistant to run a gap report for a feature slug, for example: "Run the gap report for the checkout feature and tell me which use cases from the TRD are not implemented yet."