skills.rest
gotalab
gotalabCOMMUNITY
Explore all skills by this author →
𝕏@gota_baraGitHub

kiro-validate-impl

Validate multi-task feature integration and produce GO, NO-GO, or MANUAL_VERIFY_REQUIRED decisions.

3.6k|274|Updated Jul 17, 2025
Search Tags:#spec-driven#integration#validation#kiro#tests#boundary-audit
One-click install
npx skills add https://github.com/gotalab/cc-sdd --skill kiro-validate-impl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-validate-impl
Source: https://github.com/gotalab/cc-sdd/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-validate-impl
Command: npx skills add https://github.com/gotalab/cc-sdd --skill kiro-validate-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that a feature composed of multiple implemented tasks integrates correctly end-to-end by checking cross-task contracts, full test execution, runtime liveness, requirements coverage, and design alignment so that boundary violations or hidden dependencies are caught before release.

Core Features & Use Cases

  • Full-suite validation: Runs the repository's canonical test commands and a smoke boot to confirm runtime liveness.
  • Cross-task integration checks: Verifies that Task A outputs match Task B inputs, shared state is consistent, and APIs/contracts align across tasks.
  • Design and requirements mapping: Maps requirements.md and design.md to implemented tasks and highlights coverage gaps and architectural drift.
  • Boundary audit and ownership: Detects boundary spillover, upstream vs local ownership, blocked tasks, and produces actionable GO/NO-GO or MANUAL_VERIFY_REQUIRED verdicts.
  • Use Case: Run a feature-level validation for a multi-task feature like user-auth to ensure tests pass, data flows match design, and no hidden dependencies were introduced.

Quick Start

Run kiro-validate-impl for the feature user-auth to perform full integration validation including tests, smoke boot, requirements mapping, and a boundary audit.

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 for a multi-task feature?▼

Cross-task integration validation checks that outputs from one task match the inputs of another by verifying shared state consistency, API contracts, and boundary integrity across implemented components. This Skill discovers canonical test commands to produce a final GO, NO-GO, or MANUAL_VERIFY_REQUIRED decision.

What is a boundary audit in spec-driven development?▼

A boundary audit in spec-driven development detects boundary spillover and hidden dependencies by mapping requirements and design files to implemented tasks. It identifies upstream versus local ownership issues and blocked tasks to ensure no architectural drift occurred during feature assembly.

How do I check requirements coverage and design alignment before release?▼

Requirements coverage and design alignment are checked by mapping requirements.md and design.md directly to implemented tasks. This process highlights coverage gaps, verifies that data flows match the original design, and ensures no hidden dependencies were introduced across the feature.

Can I run a smoke boot and full test suite to confirm runtime liveness?▼

Yes, you can confirm runtime liveness by discovering and running the repository's canonical test commands alongside a smoke boot. This full-suite validation verifies that the assembled feature operates correctly at runtime and that all cross-task contracts execute successfully.

Do I need spec and task files to perform feature-level integration validation?▼

Yes, spec and task files are required inputs to perform feature-level integration validation. The validation process depends on these files to map requirements to implementations, execute test suites, and generate an actionable GO, NO-GO, or MANUAL_VERIFY_REQUIRED verdict for the feature.

Why does cross-task contract validation fail when tests pass individually?▼

Cross-task contract validation can fail despite passing individual tests due to boundary violations, mismatched API contracts between tasks, or hidden dependencies. The validation catches these integration issues by checking shared state consistency and running full-suite tests across the assembled feature.

Related Skills

Explore More Software Engineering Skills→
BarryYinBarryYin

kiro-validate-impl

Validate feature-level integration and cross-task consistency across implemented tasks.

Community
Advanced
adolfoaranaes12adolfoaranaes12
2

quality-gate

Synthesize quality assessments into a go/no-go decision with YAML and Markdown reports.

Community
Advanced
FredAntBFredAntB
144

spec-driven-development

Generate requirements.md, design.md, and tasks.md with cross-AI configuration files.

Community
Advanced
jmaglyjmagly
175

gate-evaluation

Validate phase-gate criteria and generate pass/fail gate reports.

Community
Advanced