kiro-validate-gap

Gap analysis between requirements and codebase compares formal feature specs against existing modules to reveal missing capabilities and integration constraints. It evaluates extend, new, or hybrid implementation approaches to expose design readiness issues before development.

You need gap analysis for brownfield features during planning, integration scoping, or design readiness checks. It reveals missing data models, required dependencies, and integration points that must be resolved before designing new capabilities into an existing architecture.

Evaluating extend, new, or hybrid implementation approaches involves searching the codebase for patterns and integration points. This comparison estimates effort and risk for each path, flagging research items and trade-offs to determine the most viable architectural approach.

Spec.json and requirements.md provide the formal feature definitions needed to scope integration points. Loading these steering files maps requirements against existing code artifacts, evaluating architectural surfaces and generating options with effort and risk annotations.

The best way to document implementation risks and missing data models is to generate a research.md file. This document lists missing capabilities, integration points, required dependencies, and recommended implementation paths with annotated effort and risk trade-offs.