kiro-validate-design

To check implementation readiness, conduct an interactive design review that reads your spec.json, requirements.md, and design.md to validate architecture, consistency, and traceability. This process identifies critical risks and delivers a GO/NO-GO decision with actionable next steps before development begins.

A go-no-go decision in technical design review is a verdict determining if a feature's architecture is safe to implement without major rework. It is delivered with rationale and actionable next steps after validating requirements traceability and identifying up to three critical issues.

To ensure requirements traceability in your design document, run an interactive review that cross-references spec.json and requirements.md against design.md. This validates consistency and grounds assessments in project context, producing evidence-linked findings for critical issues.

You need an interactive design review before sprint planning when you want to confirm a feature's architecture and integration approach are implementable. It surfaces the highest-impact readiness gaps and delivers a GO or NO-GO decision to prevent major rework during development.

A key limitation of this design validation is its critical-issue focus, capping output at three highest-impact concerns. It requires interactive engagement for clarifications and relies on existing spec.json, requirements.md, and design.md files rather than generating missing design artifacts.