gap-report

Compares TRD use cases against source code to report implementation gaps.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill gap-report-asengardeon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gap-report
Source: https://github.com/asengardeon/btt-sdd-pipeline/tree/main/plugins/btt-sdd/skills/gap-report
Command: npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill gap-report-asengardeon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

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."

Frequently Asked Questions about gap-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which TRD use cases are implemented in code?▼

Run the gap report script with the feature slug: scripts/sdd-gap-report.sh <slug> on Bash or sdd-gap-report.ps1 -Slug <slug> on PowerShell. It parses section 6 of specs/<slug>/trd.md and greps for each use case class name in src/ and frontend/, returning a table with implementation status and evidence files.

How do I run the gap report on a project with a custom folder structure?▼

Pass your code directories as extra arguments instead of editing the script, for example sdd-gap-report.sh my-feature src/app/Application/UseCases. The provided paths replace the default auto-detection of src/ and frontend/.

Does the gap report work on Windows PowerShell?▼

Yes, a dedicated PowerShell script (sdd-gap-report.ps1) is included alongside the Bash version. It accepts -Slug (required) and -SearchPaths (optional) parameters and produces the same comparison table.

Why does the gap report show NÃO for a use case that is implemented?▼

The script uses plain text search for class names, not AST parsing, so renamed classes or implementations outside the searched directories produce false negatives. Confirm any NÃO result with a targeted manual read or additional grep before treating it as unimplemented.

What are the limitations of the TRD gap analysis?▼

It only parses the use case table in TRD section 6 and relies on naming conventions, so non-standard table formats require manual reading. It also does not check QA or security approval status, which live in separate qa-report.md and security-review.md artifacts.