skills.rest
taku-o
taku-oCOMMUNITY
Explore all skills by this author →
Website𝕏@taku_oGitHub

kiro-validate-impl

Validate cross-task integration and boundary adherence with a GO/NO-GO verdict.

1|Updated Apr 15, 2026
Search Tags:#integration#validation#boundary#test-automation#go-no-go#cross-task
One-click install
npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-validate-impl-taku-o
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-validate-impl
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-validate-impl
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-validate-impl-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate cross-task integration and boundary adherence after all tasks are implemented, ensuring consistent interfaces and complete coverage.

Core Features & Use Cases

  • Cross-task boundary verification across implemented features
  • Full test-suite execution and requirements coverage assessment
  • Boundary seam and interface compatibility checks for data flows between tasks

Quick Start

Run kiro-validate-impl with a feature name to initiate cross-task validation and receive a GO/NO-GO verdict.

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 all features?▼

Cross-task integration validation checks boundary adherence and interface consistency across implemented features by running static analysis, test execution, and integration checks to produce a GO/NO-GO verdict.

What is a GO/NO-GO verdict for feature integration testing?▼

A GO/NO-GO verdict is the final assessment result of cross-task validation, indicating whether all implemented features pass integration checks, tests, and coverage requirements for release readiness.

When do I need to run end-to-end boundary verification across multiple tasks?▼

End-to-end boundary verification is needed after all tasks are implemented to ensure cross-task consistency, interface compatibility, and complete test coverage before final integration approval.

How do I check interface compatibility for data flows between implemented tasks?▼

Interface compatibility for data flows is checked using static analysis and integration checks that verify boundary seams and cross-task consistency against design boundaries and task specs.

Can I assess requirements coverage and test results across all implemented features?▼

Yes, requirements coverage is assessed by executing the full test-suite and analyzing test results alongside task specs to confirm outputs align and coverage meets requirements for a GO verdict.

Related Skills

Explore More Software Engineering Skills→
ryu-satoryu-sato

kiro-review

Review task implementations against approved specs and boundary scope.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

production-deployment-phase

Promote validated staging builds to production with semantic versioning and health checks.

Community
Advanced
rube-derube-de
10

test

Detect test frameworks, run suites with coverage, and report findings as a GitHub issue.

Community
Advanced
ryowatanaberyowatanabe

kiro-validate-impl

Validates cross-task integration issues with full test execution and boundary audits.

Community
Advanced