kiro-review

Task review validates code diff alignment against approved requirements and design documents, detecting boundary violations and design drift. It produces a formal APPROVED or REJECTED decision with mechanical verification evidence and required remediation guidance.

Spec compliance verification is an adversarial review mechanism that checks a completed implementation against approved boundaries and requirements. It enforces mechanical checks and produces explicit remediation guidance to ensure work stays within defined task governance limits.

Run mechanical validation checks by reviewing the prepared diff after READY_FOR_REVIEW or remediation. The process evaluates implementation completeness against approved specifications and generates formal findings with severity levels and a concise acceptance summary.

Perform an adversarial task review after READY_FOR_REVIEW status, after remediation cycles, or before final acceptance. This timing ensures the implementation is real, complete, bounded, and aligned with approved design documents before integration.

Boundary violation detection requires approved requirements and design documents as reference baselines. Without these specifications, the review cannot detect design drift, missing components, or boundary violations because there are no approved constraints to validate against.

Enforce task boundaries during code review by applying a task-local adversarial review process that checks implementation against approved requirements. This approach captures boundary violations and missing components with mechanical verification evidence before acceptance.