kiro-validate-gap

Analyze implementation gaps between requirements and existing codebase.

3.6k|274|Updated Jul 17, 2025
One-click install
npx skills add https://github.com/gotalab/cc-sdd --skill kiro-validate-gap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-validate-gap
Source: https://github.com/gotalab/cc-sdd/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-validate-gap
Command: npx skills add https://github.com/gotalab/cc-sdd --skill kiro-validate-gap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces uncertainty when integrating new features into an existing codebase by systematically identifying the gap between formal requirements and what the codebase currently provides, so teams can choose viable implementation strategies with fewer surprises.

Core Features & Use Cases

  • Codebase Analysis: Search and read repository files to find existing implementations, integration points, and architecture patterns relevant to the feature.
  • Research & Validation: Perform external dependency checks and technical research to surface compatibility risks and known integration challenges.
  • Actionable Outputs: Evaluate multiple implementation approaches, document trade-offs, flag research needs, and persist a gap analysis to the feature's specs for use in design and planning.
  • Use Case: Ideal for brownfield projects where a product manager or engineer needs a clear assessment of what to build, extend, or refactor before designing the implementation.

Quick Start

Ask the agent to run kiro-validate-gap for the target feature to generate and save a gap analysis into the feature's specs research.md.

Frequently Asked Questions about kiro-validate-gap

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

FAQPage Schema
How do I identify integration gaps between new requirements and an existing codebase?

To identify integration gaps, you analyze formal requirements against the current codebase to find missing capabilities and integration risks. This gap analysis systematically evaluates implementation approaches and documents trade-offs for smoother brownfield feature integration.

How do I perform spec-driven onboarding for an existing codebase?

Spec-driven onboarding starts by reconciling formal requirements with current source code and architecture. You search repository files for integration points and perform external dependency checks to produce a comprehensive gap analysis document.

Can I evaluate multiple implementation approaches for a new feature integration?

Yes, evaluating multiple implementation approaches involves analyzing the gap between requirements and existing architecture. The analysis documents trade-offs, flags compatibility risks, and identifies missing capabilities to help teams choose viable implementation strategies.

What are the limitations of gap analysis for integration planning?

Gap analysis limitations include reliance on the accuracy of formal requirements and the completeness of codebase searches. While it surfaces integration risks and compatibility challenges, it cannot predict all runtime issues or fully replace prototyping for complex external dependencies.