kiro-reviewlisted

# kiro-review ## Overview This skill performs task-local adversarial review. It verifies that the implementation is real, complete, bounded, aligned with approved requirements and design, and supported by mechanical verification evidence. Boundary terminology continuity: - discovery identifies `Boundary Candidates` - design fixes `Boundary Commitments` - tasks constrain execution with `_Boundary:_` - review rejects concrete `Boundary Violations` ## When to Use - After an implementer reports `READY_FOR_REVIEW` - After remediation for a rejected review - Before marking a task `[x]` - Before accepting a task into feature-level validation Do not use this skill to invent missing requirements or silently reinterpret the spec. ## Inputs Provide: - Task ID and exact task text from `tasks.md` - Relevant requirement section numbers - Relevant design section numbers - Spec file paths (`requirements.md`, `design.md`, optionally `tasks.md`) - The implementer's status report - The task `_Boundary:_` scope constraints - Validation commands discovered by the controller - Relevant steering excerpts when applicable - Relevant `## Implementation Notes` entries when applicable ## Outputs Return one of: - `APPROVED` - `REJECTED` Also return: - Mechanical results - Findings with severity - Required remediation - One-sentence summary Use the language specified in `spec.json`. ## First Action Run `git diff` to inspect the actual code changes. If the diff is large or ambiguous, read the