kiro-review

Spec validation reviews task diffs against requirements.md, design.md, and tasks.md to enforce alignment with boundary constraints. It provides mechanical verification results to determine acceptance readiness after an implementer reports completion.

Task boundary compliance ensures implementation diffs stay within approved scope. Mechanical verification applies automated checks against task artifacts and diff output to document whether boundary concepts and evidence align with approved specs.

Diff analysis for task acceptance requires accessing task artifacts including requirements.md, design.md, and tasks.md alongside the implementer's status and diff output. The review enforces strict evaluation with mechanical checks to verify alignment across boundary concepts and evidence.

Yes, task spec validation requires access to task artifacts including requirements.md, design.md, and tasks.md. These files provide the approved specs and task boundaries needed to enforce alignment and verify scope compliance against the implementation diff.

Run spec validation and boundary checks after an implementer reports READY_FOR_REVIEW, after remediation, or before accepting a task as complete. This timing ensures alignment is verified when the implementation diff is ready for mechanical verification and documented outcomes.

The best way to verify boundary compliance is running a rigorous review against approved specs, task boundaries, and verification evidence. This enforces strict evaluation with mechanical checks and provides suggested remediation to address alignment gaps before acceptance.