skills.rest
BarryYin
BarryYinCOMMUNITY
Explore all skills by this author →
GitHub

kiro-validate-impl

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

Updated Apr 17, 2026
Search Tags:#spec-driven#validation#integration-testing#test-suite#hermes#design-alignment#boundary-audit
One-click install
npx skills add https://github.com/BarryYin/Hermes-sdd --skill kiro-validate-impl-barryyin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-validate-impl
Source: https://github.com/BarryYin/Hermes-sdd/tree/main/skills/kiro-validate-impl
Command: npx skills add https://github.com/BarryYin/Hermes-sdd --skill kiro-validate-impl-barryyin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill detects integration-level defects that only appear when multiple implemented tasks are combined, ensuring that completed tasks, tests, and design commitments form a coherent, deployable feature without boundary violations or hidden dependencies.

Core Features & Use Cases

  • Full-suite validation: Runs canonical test and smoke commands to confirm the entire feature passes integration-level checks beyond per-task tests.
  • Cross-task contract verification: Compares task outputs and inputs, shared state, and API/data shapes to catch mismatches and boundary spillover.
  • Requirements and design alignment: Maps requirements and design sections to implemented tasks and highlights coverage gaps or architectural drift.
  • Use Case: After implementing a user-auth feature composed of multiple tasks, run this skill to ensure the login flow, session handling, database schema, and API contracts work together and that the full test suite and smoke checks pass.

Quick Start

Run kiro-validate-impl against the completed feature to verify tests, smoke boot, cross-task contracts, and requirements coverage.

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 after completing multiple spec-driven tasks?▼

Feature-level integration validation runs full test suites and smoke checks across completed tasks to confirm cross-task consistency, catch boundary spillover, and produce GO/NO-GO evidence for deployment readiness.

What is cross-task contract verification and why do I need it?▼

Cross-task contract verification compares task outputs, inputs, shared state, and API or data shapes to detect mismatches and boundary violations that only surface when multiple implemented tasks are combined into a single feature.

How do I map requirements to implementations in a spec-driven development repository?▼

Mapping requirements to implementations involves tracing spec sections to completed tasks and test results to highlight coverage gaps, architectural drift, and unfulfilled design commitments before release.

Does feature integration validation work with existing project test and build commands?▼

Feature integration validation requires access to your repository files, project test and build commands, and smoke commands to execute full test suites and generate deployable GO/NO-GO evidence.

When should I run an end-to-end integration boundary audit?▼

An integration boundary audit should be run after implementing a feature composed of multiple tasks, such as a user-auth flow, to ensure login, session handling, database schema, and API contracts work together without hidden dependencies.

Related Skills

Explore More Software Engineering Skills→
notta50notta50

kiro-spec-status

Parse spec metadata and markdown task lists to report phase progress.

Community
Intermediate
alex-voloshin-devalex-voloshin-dev
2

spike

Conduct time-boxed technical research and feasibility analysis for architectural unknowns.

Community
Advanced
bostonaholicbostonaholic
8

test-driven-bug-fix

Reproduce, isolate, fix, and verify software defects using test-driven methodology.

Community
Advanced
misadecastromisadecastro

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for consistency and quality gaps.

Community
Intermediate