Analyze Requirements

Before moving from requirements to design, you can ask Kiro to analyze your requirements for logical inconsistencies, ambiguities, and gaps. This deep analysis reasons across your full requirement set — not just each requirement in isolation — to find issues that are hard to catch in a read-through.

• Logical inconsistencies — two requirements that individually make sense but are collectively impossible
• Ambiguities — language like "large files" or "fast response times" that would produce divergent implementations
• Conflicting constraints — functional and non-functional requirements that can't all be satisfied at once
• Unstated assumptions — references to undefined concepts or behaviors
• Missing edge cases — failure modes, boundary conditions, and concurrent access scenarios not covered by the happy path

After requirements are generated, you'll see Analyze Requirements as an option in two places:

• In chat, alongside the other options for how to proceed
• In the Continue dropdown in the editor, alongside Proceed to Design

The analysis takes minutes, not seconds — cross-requirement reasoning is more computationally intensive than typical Kiro operations. As findings are ready, clarifying questions stream into chat.

Each question includes the requirements involved, a plain-language explanation of the issue, and suggested fixes you can select. You can also type a custom answer or dismiss a question if the ambiguity is intentional. As you resolve questions, Kiro updates requirements.md in the editor.

Analysis is especially valuable for complex features with many requirements, domain-sensitive projects (financial services, healthcare, compliance), and Quick Plan sessions where requirements were auto-generated without manual review. For small or well-understood specs, you can skip the analysis and proceed directly to design.

You can re-run the analysis after editing requirements manually — Kiro will re-analyze affected requirements and their interactions.