What problem does it solve? Design documents often drift from what the codebase actually supports, and teams discover breaking changes, missing failure handling, or wrong dependency directions only during implementation. This Skill runs an adversarial, code-grounded review of a finished design before any code is written, catching blocking issues while they are still cheap to fix. ## Core Features & Use Cases - Adversarial Design Review: Diffs the design against verified codebase reality using reflection lenses covering contracts, blast radius, idempotency, failure paths, concurrency, authorization, and observability. - Evidence-Backed Findings: Every blocking issue carries a code reference (repo path, line, class, method) so findings are grounded in fact rather than opinion. - GO/NO-GO Gate with Audit Trail: Updates approval fields in spec.json, persists the full review to design-review.md, and records learnings for future specs. - Use Case: After generating a design for a new notifications feature, run the validation gate to confirm the design handles retries, respects existing API contracts, and does not break current callers before generating implementation tasks. ## Quick Start Ask the assistant to validate the design for your feature by running the kiro-validate-design skill with your feature name, for example: validate the design for my-feature before we start implementation.
