kiro-review

To verify task implementations meet approved specs, you review actual diffs and status reports against requirements and design references. This mechanical review enforces strict boundary-respecting evaluation to confirm compliance.

Mechanical verification for code review is the process of checking actual implementation diffs and status reports against approved specs and boundaries. It outputs a binary verdict, mechanical results, and findings with severity levels to determine acceptance.

You need to run a spec compliance review after implementation milestones such as READY_FOR_REVIEW, after remediation, or before final acceptance. It ensures the implementation respects task boundaries and meets the approved requirements.

Boundary-aligned task verification requires the task ID, relevant requirements and design references, the implementer's status report, and the task boundary scope. These inputs enable a formal review to determine acceptance and identify remediation steps.

Yes, spec compliance review works without dependencies. It operates independently to review task implementations against approved specs, boundaries, and verification evidence to determine acceptance and output remediation steps.

Code review checking spec compliance produces a binary verdict, mechanical results, findings with severity levels, required remediation steps, and a concise summary. These outputs determine whether the task implementation is accepted or needs further work.