kiro-validate-impl

Detect and verify cross-task integration after all kiro tasks are implemented.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ryu-sato/reading-web-supporter --skill kiro-validate-impl-ryu-sato
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-validate-impl
Source: https://github.com/ryu-sato/reading-web-supporter/tree/main/.claude/skills/kiro-validate-impl
Command: npx skills add https://github.com/ryu-sato/reading-web-supporter --skill kiro-validate-impl-ryu-sato

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and verify cross-task integration after all tasks are implemented. It also ensures boundary integrity, cross-task consistency, and comprehensive spec coverage.

Core Features & Use Cases

  • Cross-task consistency checks across kiro tasks
  • End-to-end validation of feature implementations
  • Design alignment verification and boundary integrity checks

Quick Start

Detect cross-task integration and run the full validation workflow for a target 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 cross-task integration after implementing multiple feature tasks?

Cross-task integration validation detects and verifies data flow consistency across completed kiro tasks. It enforces canonical validation steps, boundary alignment, and design-constraint checks to ensure feature-level consistency after all tasks are implemented.

What is cross-task consistency checking in a multi-task feature workflow?

Cross-task consistency checking verifies boundary integrity and data flow alignment across multiple implemented kiro tasks. It ensures comprehensive spec coverage and validates that individual task implementations integrate correctly at feature boundaries.

How do I run end-to-end validation for a feature built across separate tasks?

End-to-end validation runs the full kiro validation workflow for a target feature, verifying design alignment and boundary integrity. It automatically detects cross-task integration points and enforces canonical validation steps across all implemented tasks.

Do I need all tasks implemented before running cross-task feature validation?

Cross-task feature validation requires all related kiro tasks to be implemented first. It is designed to verify integration, boundary alignment, and data flow consistency after task completion, not during incremental development stages.

What's the best way to ensure design alignment and boundary integrity across implemented tasks?

Automated cross-task validation enforces design-constraint checks and boundary alignment as defined by the kiro validation workflow. It verifies that task boundaries match design specifications and maintains data flow consistency across the feature implementation.

Why does my feature fail test coverage when individual tasks pass their own tests?

Individual task tests may not cover cross-task boundary seams and integration points. Cross-task validation enforces comprehensive spec coverage and verifies data flow consistency across task boundaries to detect integration gaps missed by isolated task tests.