kiro-validate-design

To validate design readiness, apply a structured review process to feature-level designs, load project steering context, and generate a GO/NO-GO decision with prioritized improvements and rationale.

A GO/NO-GO decision in design review is a clear recommendation determining whether a technical design is ready for implementation, delivered with actionable next steps and explicit rationale.

You need a structured design review when a feature design draft is ready for evaluation, requiring context-aware assessment of critical issues, strengths, and improvement opportunities before implementation.

Yes, you can assess risk and identify design issues across codebases by loading relevant design artifacts and project steering context to perform an interactive quality review.

The best way to ensure traceability during spec analysis is to load project steering context alongside relevant design artifacts, applying a defined review process to validate requirements and architecture alignment.

Without a guided design review process, teams risk missing critical design issues, lacking architecture alignment, and proceeding to implementation without a structured GO/NO-GO rationale or risk assessment.