kiro-validate-design

A technical design review validates architecture alignment, requirements traceability, and extensibility by reading spec.json, requirements.md, and design.md to produce a GO/NO-GO decision with prioritized critical issues.

Requirements traceability validation checks that design documents explicitly map to requirements, ensuring architecture alignment and type safety before engineering work starts. It identifies up to three critical gaps needing remediation.

You validate architecture alignment by loading feature-level spec and design documents into an interactive review process that engages the designer to clarify tradeoffs, surfacing maintainability concerns and missing traceability.

Yes, design validation can limit findings to the top three prioritized critical issues with evidence from the design document, providing clear rationale and concrete remediation steps instead of an exhaustive list.

You need design validation before starting engineering work on a new feature to surface architectural misalignments, verify type safety, and ensure your steering context and language settings are respected for task generation.

Yes, interactive design validation operates without external dependencies or components, reading local spec.json, requirements.md, and design.md files directly to return actionable GO/NO-GO recommendations.