What problem does it solve? After individual tasks are implemented and reviewed, integration issues can still hide between tasks: mismatched interfaces, requirement gaps, architectural drift, and boundary violations. This Skill performs a final feature-level validation gate before declaring work complete. ## Core Features & Use Cases - Mechanical Validation: Runs the full test suite, greps for residual TODO/FIXME markers and hardcoded secrets, and performs a runtime smoke boot check. - Cross-Task Judgment Checks: Verifies interface contracts, shared state consistency, requirements coverage, design alignment, and boundary integrity across all completed tasks. - Structured GO/NO-GO Report: Produces a decision report with mechanical results, coverage mapping, ownership classification (LOCAL/UPSTREAM/UNCLEAR), and mandatory remediation steps on failure. - Use Case: After running implementation for a user-auth feature across tasks 1.1 through 1.3, invoke validation to confirm the full test suite passes, all requirements are covered, and no cross-task integration seams leak before shipping. ## Quick Start Ask the agent to validate the implemented feature, for example by saying: run kiro-validate-impl on the user-auth feature and give me the GO or NO-GO report.
