kiro-validate-impl

To validate cross-task integrity, run the kiro-validate-impl workflow against your latest implementations. This verifies that interfaces, data contracts, and dependencies remain consistent with the overall design and identifies any integration gaps requiring coordination.

End-to-end alignment verification maps every requirement to at least one implemented task to ensure traceability. It compares implementations against design.md and boundary commitments to detect drift, identify coverage gaps, and confirm the full test suite is satisfied.

Yes, design alignment checking directly compares your implementations against design.md and boundary commitments. This detects drift and misaligned boundaries early, ensuring that your cross-task data flows and interfaces match the originally intended project design.

Yes, automated coverage mapping maps every requirement to at least one task and identifies gaps requiring cross-task coordination. This replaces manual traceability checks by automatically verifying interfaces, data contracts, and full test suite satisfaction.

Run cross-task boundary audits immediately after feature implementations to detect drift and misaligned boundaries. Applying canonical validation steps early prevents boundary violations and integration gaps from compounding across your multi-task project.