kiro-validate-gap

Gap analysis between requirements and a codebase involves loading specs and repository context to identify missing capabilities, unknowns, and risks, producing a structured research document for implementation planning.

Feature-oriented gap analysis is the structured process of comparing approved requirements against existing modules, architectures, and integrations to surface constraints and generate actionable design inputs.

Generate traceability documentation by reading approved specs and steering content against the repository to identify missing capabilities, outputting a structured gap-analysis document with actionable findings.

You need a gap analysis for implementation planning when transitioning from approved requirements to design, requiring the identification of unknowns, constraints, and missing capabilities across target modules.

Yes, gap analysis applies to feature-oriented assessments across modules and integrations, surfacing risks and constraints to produce actionable research items that directly inform downstream design decisions.

Limitations of codebase gap analysis include its dependency on accurate prerequisite specs and steering content; it produces research items and design inputs but does not directly execute code modifications or implement features.