kiro-validate-gap

Analyze implementation gaps between requirements and an existing codebase.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-validate-gap-taku-o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-validate-gap
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-validate-gap
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-validate-gap-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes and documents the gap between project requirements and the existing codebase to inform implementation strategy.

Core Features & Use Cases

  • Gap discovery: Identify missing capabilities, conflicting dependencies, and architectural gaps.
  • Option evaluation: Compare multiple implementation approaches (extend, create, hybrid) with trade-offs.
  • Research-driven planning: Produce a formal gap analysis document and identify research needs for design.

Quick Start

Run a gap analysis against the target feature to identify missing capabilities and integration challenges.

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 the gap between project requirements and an existing codebase?

Gap analysis identifies missing capabilities, conflicting dependencies, and architectural gaps between project requirements and an existing codebase to inform your implementation strategy and research needs.

What is the best way to evaluate implementation options for system integration projects?

Evaluating implementation options involves comparing extend, create, and hybrid approaches with their trade-offs to determine the most effective strategy for integrating new features into existing systems.

Can I use gap analysis to discover missing capabilities during feature planning?

Yes, gap analysis assesses current patterns, components, and interfaces during feature planning to identify missing capabilities and integration challenges before development begins.

How does a structured gap analysis document help with research-driven planning?

A structured gap analysis document formalizes discovered implementation gaps and research needs, providing a clear foundation for design decisions and downstream development planning.

When should I perform a requirement-to-code gap analysis instead of direct implementation?

Perform gap analysis when adding complex features or integrating systems to uncover conflicting dependencies and architectural risks early, ensuring your chosen implementation approach aligns with existing patterns.