{extends: review-qa}

## Kiro Skill Source

Before executing this instruction, invoke `$kiro-validate-gap` or `/kiro-validate-gap` and read the resolved `SKILL.md`.
Apply the `## Core Task` section from `$kiro-validate-gap` or `/kiro-validate-gap` as this step's source of truth.
This facet defines only the adapter delta for the TAKT workflow.

# Kiro Gap Validation Readiness

## Kiro-specific delta

This instruction is read-only. Inspect requirements and current codebase evidence, but do not write `.kiro/*` artifacts.

## Validation procedure

1. Verify that `.kiro/specs/<feature>/requirements.md` exists and that `spec.json` has reached a requirements-capable phase.
2. If requirements are missing or the lifecycle is inconsistent, return `DECISION: NO-GO` with `error_category: ARTIFACT_MISSING` or `LIFECYCLE_INCONSISTENT`.
3. Compare requirements against existing implementation evidence.
4. Record existing implementation, missing components, integration points, and recommended next action.
5. Record observed evidence and missing evidence separately in `evidence` and `findings`.
6. If codebase evidence is insufficient, return `DECISION: MANUAL_VERIFY_REQUIRED`, add a finding with `category: "MANUAL_VERIFICATION_REQUIRED"`, and do not treat that item as verified evidence.

## Output mapping

Use the shared `kiro-validation-result` contract. Always set `DECISION` as the primary workflow-routing field: `GO` for complete validation, `NO-GO` for failed validation, and `MANUAL_VERIFY_REQUIRED` when codebase evidence cannot be confirmed automatically. Put stopping reasons in `findings.message` and verified facts in `evidence`.
