Individual skill
kiro-validate-impl
Validate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.
tools/cc-sdd/templates/agents/gemini-cli-skills/skills/kiro-validate-impl/SKILL.md
Source commit e2a0c671aef37a482404905b409ab5c27092b25b
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,757
- Repository last updated
- Oct 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- steering Repository topic
- kiro Repository topic
- spec-driven-development Repository topic
- cursor Repository topic
- claude-code Repository topic
- codex Repository topic
- gemini-cli Repository topic
- github-copilot Repository topic
- subagents Repository topic
- opencode Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 11,865 bytes
Read excerpt
# Implementation Integration Validation
<background_information>
Individual tasks are usually reviewed 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`
- **Success Criteria**:
- All tasks marked `[x]` in tasks.md