What problem does it solve? Before writing requirements or design, teams often guess whether the codebase already supports a requested change. This Skill investigates what the repository actually provides, names precisely what is missing, unknown, or constrained, and hands the next phase evidence it can decide from—without making the decision itself. ## Core Features & Use Cases - Evidence-based investigation: Dispatches fresh readers to examine what exists, what constrains it, and what the work must meet, reading actual code rather than plausible assumptions. - Routing of findings: Sends discoveries that change what is being asked back to the user before touching the brief, while design constraints flow to the design phase instead of polluting requirements. - Optional research artifact: Writes a research document only when findings outlive the analysis, marking each conclusion for its proper destination (Brief, Requirements, Design, Steering, or none). - Use Case: After a new feature request is routed to a spec, run this analysis to discover that a similar module already exists but restricts how the work can be done—recording that as design input rather than a requirement. ## Quick Start Use the sb-gap-analysis skill to compare the intended work for this spec against what the repository already provides and report what is missing, unknown, or constrained.
