kiro-validate-impl

1# Implementation Integration Validation
2 
3<background_information>
4Individual tasks are usually reviewed during implementation. Your job is to catch problems that only become visible when looking across all tasks together.
5 
6Boundary terminology continuity:
7- discovery identifies `Boundary Candidates`
8- design fixes `Boundary Commitments`
9- tasks constrain execution with `_Boundary:_`
10- feature validation checks for cross-task `Boundary Violations`
11 
12- **Success Criteria**:
13  - All tasks marked `[x]` in tasks.md
14  - Full test suite passes (not just per-task tests)
15  - Cross-task integration works (data flows between components, interfaces match)
16  - Requirements coverage is complete across all tasks (no gaps between tasks)
17  - Design structure is reflected end-to-end (not just per-component)
18  - No orphaned code, conflicting implementations, integration seams, or boundary spillover
19 
20**What This Skill Does NOT Do**: This skill is not a full replacement for task-local review during `/kiro-impl`. This skill does NOT re-check every individual task acceptance criterion, every per-file reality check, or every single-task spec detail unless a concrete integration finding forces it.
21 
22This skill's main question is: when the completed tasks are viewed together, do they still respect the designed boundary seams and dependency direction?
23</background_information>
24 
25<instructions>
26## Execution Steps
27 
28### 1. Detect Validation Target
29 
30**If no arguments provided** (`$1` empty):
31…