kiro-validate-impl

Validate feature-level integration across all implemented tasks with full test suite checks.

8|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/gaebalai/k-sdd --skill kiro-validate-impl-gaebalai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-validate-impl
Source: https://github.com/gaebalai/k-sdd/tree/main/tools/k-sdd/templates/agents/claude-code-skills/skills/kiro-validate-impl
Command: npx skills add https://github.com/gaebalai/k-sdd --skill kiro-validate-impl-gaebalai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Validates feature-level integration after tasks are implemented, ensuring cross-task consistency, full test suite, and complete spec coverage.

Core Features & Use Cases

  • Cross-Task Consistency: Checks for boundary violations and cross-task integration issues.
  • Full Test Suite: Verifies that all tests pass and identifies any gaps.
  • Spec Coverage: Ensures requirements and design are fully covered.

Quick Start

Run kiro-validate-impl <feature-name> to validate the integration of the specified feature.

Frequently Asked Questions about kiro-validate-impl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate feature-level integration across multiple development tasks?

Feature-level integration is validated by running the full test suite and checking for boundary violations to ensure cross-task consistency and completeness within a specified feature.

What is cross-task consistency checking in software development workflows?

Cross-task consistency checking verifies that individual development tasks integrate seamlessly, identifying boundary violations and integration issues to maintain feature-level consistency.

How do I ensure spec coverage after implementing feature tasks?

Spec coverage is ensured by validating that the implemented feature fully covers the requirements and design, while running the full test suite identifies any remaining gaps.

Can I check for boundary violations across all tasks within a single feature?

Yes, boundary violations are checked across all tasks within a specified feature to ensure cross-task consistency, requiring the full test suite to pass for complete validation.

What's the best way to verify that all tests pass after integrating feature tasks?

The best way to verify all tests pass is to run the full test suite for the specified feature, which simultaneously checks for boundary violations, spec coverage, and cross-task integration.

Why does my feature validation fail when individual tasks pass their tests?

Feature validation fails because cross-task integration issues and boundary violations exist between tasks, which individual task tests do not detect but the full test suite exposes.