kiro-validate-gap

Analyzes the gap between feature requirements and the existing codebase to inform design decisions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/scapia-oss/compass --skill kiro-validate-gap-scapia-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-validate-gap
Source: https://github.com/scapia-oss/compass/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-validate-gap
Command: npx skills add https://github.com/scapia-oss/compass --skill kiro-validate-gap-scapia-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Before designing a feature that integrates with an existing system, teams need to know what the codebase already provides, what is missing, and which integration approaches are viable. This Skill performs that gap analysis systematically and persists the findings so they survive across sessions. ## Core Features & Use Cases - Codebase Gap Analysis: Compares spec requirements against existing code patterns, components, and integration points using grep, glob, and parallel research. - Multiple Implementation Options: Evaluates extend, new-build, and hybrid approaches with trade-offs rather than prescribing a single solution. - Durable Artifacts: Writes gap-analysis.md and appends to research.md in the spec directory, and records learnings for future specs. - Use Case: When planning a brownfield feature like adding notifications to an existing app, run this after requirements approval to identify missing capabilities and integration risks before the design phase. ## Quick Start Run the kiro-validate-gap skill with a feature name to analyze how its requirements map against the current codebase and produce a gap analysis document.

Frequently Asked Questions about kiro-validate-gap

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

FAQPage Schema
How do I analyze gaps between requirements and an existing codebase?

Run the gap analysis after requirements are written: it reads requirements.md and spec.json, searches the codebase for existing patterns and integration points, then evaluates extend, new-build, and hybrid approaches. Findings are written to gap-analysis.md in the spec directory.

When should I run gap analysis in a spec-driven workflow?

Run it after requirements are generated and before the design phase, especially for brownfield projects. It is optional but recommended when a feature must integrate with existing systems, since it surfaces missing capabilities and integration risks early.

What happens if requirements.md does not exist before gap analysis?

The skill stops and instructs you to run the requirements generation command first. If requirements exist but are not yet approved, it warns you but still proceeds, since the analysis can inform requirement revisions.

Does gap analysis decide the final implementation approach?

No. It provides information and multiple viable options with trade-offs rather than final decisions. The goal is to flag technical research needs and integration challenges so the design phase can make informed choices.

Where are gap analysis results stored?

Results are written to gap-analysis.md in the resolved spec directory and a summary is appended to research.md for backward compatibility with design skills. Significant findings are also recorded in the spec's learnings.md file.