kiro-validate-impl

Cross-task integration validation is performed by executing full test suites and boundary audits to verify that all task outputs satisfy downstream inputs and align with design commitments. It generates a remediation-oriented report capturing ownership for any identified gaps.

End-to-end spec coverage validation verifies that interfaces, data contracts, and dependency directions align coherently across all implemented tasks. It ensures downstream inputs are satisfied and design commitments are upheld through comprehensive test execution and design alignment checks.

Checking data contract and interface alignment involves auditing dependency direction and verifying downstream inputs against upstream task outputs. This process enforces end-to-end coherence and highlights any misalignment through actionable remediation recommendations.

End-to-end validation is needed after all tasks in a multi-task feature set are implemented to ensure interfaces and data contracts align across the solution. It enforces full test execution, design alignment, and boundary audits to catch integration gaps.

End-to-end validation provides a remediation-oriented report that captures ownership and actionable steps for any spec coverage gaps or interface misalignments found during the cross-task integration checks.

Cross-task integration validation is limited to multi-task feature sets where interfaces and data contracts must align. It requires all tasks to be fully implemented before executing end-to-end validation steps, making it unsuitable for partial or incomplete feature workflows.