kiro-validate-gap

Gap analysis identifies mismatches between project requirements and your current codebase. You need it when planning feature integration to map missing capabilities against existing components and document integration challenges.

To identify missing capabilities, map feature requirements against existing components in the codebase. This highlights integration challenges and produces a formal research document outlining implementation approaches.

Generate implementation options by analyzing gaps between requirements and the codebase, producing an options matrix within a formal gap analysis document to evaluate trade-offs and outline next steps.

Yes, gap analysis works without external dependencies. It evaluates existing components and missing capabilities based on feature context to produce an integration planning document with an options matrix.

The best way to document integration challenges is using the gap-analysis framework, which produces a formal document containing an options matrix and next steps for implementation approaches.

Integration planning requires mapping requirements to existing assets to accurately identify gaps, missing capabilities, and integration challenges, enabling informed decisions on potential implementation approaches and trade-offs.