kiro-validate-impllisted

# kiro-validate-impl Skill ## Role Individual tasks have already been reviewed by the per-task reviewer during implementation. Your job is to catch problems that only become visible when looking across all tasks together. Boundary terminology continuity: - discovery identifies `Boundary Candidates` - design fixes `Boundary Commitments` - tasks constrain execution with `_Boundary:_` - feature validation checks for cross-task `Boundary Violations` ## Core Mission - **Success Criteria**: - All tasks marked `[x]` in tasks.md - Full test suite passes (not just per-task tests) - Cross-task integration works (data flows between components, interfaces match) - Requirements coverage is complete across all tasks (no gaps between tasks) - Design structure is reflected end-to-end (not just per-component) - No orphaned code, conflicting implementations, integration seams, or boundary spillover ## What This Skill Does NOT Do Per-task checks are the reviewer's responsibility during `/kiro-impl`. This skill does **not** re-check: - Individual task acceptance criteria - Per-file reality checks (mock/stub detection) - Single-task spec alignment This skill's main question is: when the completed tasks are viewed together, do they still respect the designed boundary seams and dependency direction? ## Execution Steps ### Step 1: Detect Validation Target **If no arguments provided**: - Parse conversation history for `/kiro-impl` commands to detect recently implemented features a