kiro-validate-gap

Analyze implementation gaps between requirements and existing codebase.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/BarryYin/Hermes-sdd --skill kiro-validate-gap-barryyin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-validate-gap
Source: https://github.com/BarryYin/Hermes-sdd/tree/main/skills/kiro-validate-gap
Command: npx skills add https://github.com/BarryYin/Hermes-sdd --skill kiro-validate-gap-barryyin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze and surface differences between a feature's written requirements and the current codebase so teams can choose a safe, realistic implementation path and identify research needs before design work begins.

Core Features & Use Cases

  • Comprehensive code-to-requirement mapping: Scans specs, requirements, and steering context to locate relevant code modules and integration surfaces.
  • Gap identification and research flags: Marks missing capabilities, unknowns that require investigation, and architectural constraints that affect feasibility.
  • Multiple implementation options: Produces extend/new/hybrid approaches with trade-offs, effort and risk estimates, and prioritized next steps for design.
  • Use Case: For a brownfield feature, generate a research-ready gap analysis that identifies what must be added or adapted and recommends whether to extend existing components or create new ones.

Quick Start

Run the kiro-validate-gap skill for the target feature to produce a research.md report mapping requirements to code and listing recommended implementation options.

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 implementation gaps between feature requirements and an existing codebase?

Gap analysis maps written requirements to existing code modules, identifies missing capabilities, and flags unknowns that require investigation before design work begins. This produces a research-ready report for safe implementation planning.

What is the best way to plan feature integration for a brownfield codebase?

Brownfield feature integration planning requires comparing specifications against repository code to locate integration surfaces and architectural constraints. Gap identification reveals whether to extend existing components or build new ones with effort and risk estimates.

How does requirement-to-code mapping work for spec-driven workflows?

Spec-driven gap analysis scans requirements and steering context to locate relevant code modules, then maps each requirement to existing assets. This reveals missing capabilities and produces extend, new, or hybrid implementation options with trade-offs.

Can I get implementation options with effort and risk estimates before starting design?

Implementation options include extend, new, and hybrid approaches with trade-offs, effort estimates, and risk notes. Prioritized next steps guide design decisions by evaluating architectural constraints and feasibility for each path.

When do I need gap analysis for a software project?

Gap analysis is needed for brownfield features, spec-driven workflows, and feature integration planning where requirements must be compared to repository code. It identifies missing capabilities and research needs before design work begins.

What does a gap analysis report include for feature planning?

A gap analysis report includes requirement-to-asset mapping, missing capabilities, architectural constraints, and recommended implementation options with effort and risk notes. It provides prioritized next steps to guide design decisions.