What problem does it solve? After individual tasks are implemented and reviewed in isolation, cross-task problems like integration seams, duplicated logic, requirement gaps, and design drift remain invisible. This Skill performs a whole-feature validation pass that catches issues only visible when all completed tasks are examined together. ## Core Features & Use Cases - Mechanical Gates: Runs the full test suite, greps for residual TODOs and hardcoded secrets, and executes a runtime smoke-boot check, returning GO, NO-GO, or MANUAL_VERIFY_REQUIRED. - Cross-Task Judgment Checks: Verifies interface contracts, shared state consistency, cross-unit code duplication, requirements coverage percentage, and end-to-end design alignment including spec-drift scans. - Shared Component Regression: Optionally dispatches a regression-verifier subagent when shared code with external callers was modified, with a --regression flag to force the check. - Use Case: After finishing all tasks of a user-auth feature, run the validation to confirm the full test suite passes, every requirement section maps to a completed task, and the implementation still matches the approved design before handoff. ## Quick Start Ask the agent to validate the completed feature by running kiro-validate-impl with the feature name, for example to validate user-auth end to end.
