kiro-validate-impl

Cross-task integration validation aggregates completed tasks, loads their specification and design context, and runs a canonical validation suite to confirm end-to-end consistency. It checks requirement coverage, data contracts, and boundary restrictions to report any drift.

End-to-end integration validation detects cross-task drift by orchestrating a full test suite, verifying requirement coverage, and assessing design alignment. It confirms interface compatibility and data contracts across all implemented tasks to ensure feature-level coherence.

Boundary alignment and data contract consistency are checked by validating specification context against implemented tasks. The validation detects boundary spillover, integration seams issues, and data contract mismatches, providing actionable remediation guidance for any gaps found.

Yes, you can invoke the validation workflow with specific tasks by providing the feature and optional task arguments. This allows targeted cross-task integration checks, loading the relevant specification and design context only for the specified task subset.

End-to-end validation works for features with boundary restrictions by explicitly confirming those restrictions during the validation suite. It checks boundary integrity across tasks to detect spillover and ensures integration seams respect the defined design boundaries.

Cross-task drift occurs when implemented tasks diverge from their shared specification and design context over time. The validation identifies these gaps by aggregating completed tasks, running full test suites, and checking requirement coverage against the original design alignment.