skills.rest
manatago
manatagoCOMMUNITY
Explore all skills by this author →
GitHub

kiro-validate-gap

Identify gaps between requirements and existing code for integration strategy.

Updated Apr 16, 2026
Search Tags:#design#planning#integration#codebase#requirements#analysis#gap-analysis
One-click install
npx skills add https://github.com/manatago/gion --skill kiro-validate-gap-manatago
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-validate-gap
Source: https://github.com/manatago/gion/tree/main/.claude/skills/kiro-validate-gap
Command: npx skills add https://github.com/manatago/gion --skill kiro-validate-gap-manatago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams uncover gaps between project requirements and the current codebase, enabling informed planning and risk mitigation.

Core Features & Use Cases

  • Systematically loads context from specifications and steering guidance, then aligns gaps with real implementation
  • Evaluates feasibility and risks by comparing requirements to existing architectures, data models, and interfaces
  • Proposes multiple viable integration approaches (extend, create, hybrid) with trade-offs and research needs
  • Generates a formal gap analysis document and stores it to disk for design-phase reference
  • Flags unknowns and constraints to guide focused investigation

Quick Start

Provide project context and request a gap analysis to surface implementation options.

Frequently Asked Questions about kiro-validate-gap

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

FAQPage Schema
What is gap analysis in software engineering and when do I need it?▼

Gap analysis identifies discrepancies between project requirements and your existing codebase to guide integration strategy. You need it during the design phase to mitigate risks and evaluate feasibility before implementing new features.

How do I identify gaps between new requirements and an existing codebase?▼

To identify codebase gaps, load project specifications and compare them against existing architectures, data models, and interfaces. This process flags unknowns and constraints to guide focused investigation into missing functionality.

How do I plan an integration strategy for new feature areas?▼

Plan an integration strategy by evaluating multiple viable approaches like extending current systems, creating new modules, or hybrid solutions. Compare their trade-offs and research needs against your architecture to produce a structured plan.

Can I use gap analysis for planning codebase dependencies and architecture changes?▼

Yes, gap analysis applies directly to feature areas across codebase, dependencies, and architecture. It systematically aligns steering guidance with real implementation to evaluate feasibility and constraints before major changes.

What is the best way to document unknowns and constraints during requirements analysis?▼

The best way to document unknowns is generating a formal gap analysis document that flags constraints and research needs. Store this structured output to disk for continuous reference during your design and planning phases.

Related Skills

Explore More Software Engineering Skills→
qlawmarqqlawmarq

sdd-validate-gap

Analyze implementation gaps between project requirements and existing codebases.

Community
Advanced
gotalabgotalab
3.6k

kiro-validate-gap

Analyze implementation gaps between requirements and existing codebase.

Community
Advanced
bordenetbordenet
8

debate

Generate and evaluate three design options with a five-criterion comparison matrix.

Community
Advanced
saitarrunsaitarrun
4

to-prd

Synthesize product conversations and codebase context into a structured PRD and publish it to the issue tracker.

Community
Intermediate