kiro-validate-gap

Analyze gaps between requirements and an existing codebase to inform implementation strategy.

Updated Feb 25, 2024
One-click install
npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-validate-gap-ryowatanabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-validate-gap
Source: https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper/tree/main/.claude/skills/kiro-validate-gap
Command: npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-validate-gap-ryowatanabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze implementation gap between requirements and existing codebase to inform planning and integration strategy.

Core Features & Use Cases

  • Gap analysis to map requirements to codebase and identify missing capabilities.
  • Evaluate integration challenges and propose multiple approaches (extend/new/hybrid).
  • Produce a research document guiding design phase and risk assessment.

Quick Start

Run a gap analysis to identify missing requirements and generate a research report.

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

Gap analysis maps software requirements against an existing codebase to identify missing capabilities and integration challenges. It produces a structured report evaluating extend, replace, or hybrid implementation approaches to inform design phase planning.

How do I evaluate whether to extend or replace modules during integration planning?

Evaluate module integration by analyzing the gap between requirements and codebase capabilities. Generate multiple implementation options including extend, replace, or hybrid solutions, each with documented trade-offs and risk assessment to guide architecture decisions.

Can I use gap analysis for interface integration across multiple modules?

Yes, gap analysis applies directly to interface integration across modules. It identifies missing capabilities between requirements and codebase, then delivers a documented research path guiding the design phase and risk assessment for those integrations.

What's the best way to document implementation strategy options for a new feature?

Document implementation strategy by running a gap analysis that maps requirements to codebase missing capabilities. Produce a research document containing structured gap analysis, multiple implementation options with trade-offs, and a research path for design.

When do I need to perform a codebase gap analysis before starting design?

Perform codebase gap analysis when planning integration across modules and interfaces, or when evaluating extend, replace, or hybrid implementation approaches. It reveals missing capabilities and delivers a research path necessary for risk assessment.