kiro-impl

Coordinate autonomous subagents to complete approved tasks using strict TDD discipline.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/snicmakino/kolt --skill kiro-impl-snicmakino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-impl
Source: https://github.com/snicmakino/kolt/tree/main/.claude/skills/kiro-impl
Command: npx skills add https://github.com/snicmakino/kolt --skill kiro-impl-snicmakino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates autonomous subagents to complete approved tasks using a strict TDD discipline.

Core Features & Use Cases

  • Autonomous & Manual Modes: Dispatch subagents to handle tasks independently or execute selected tasks in main context.
  • Strict Task Boundary: Operates within predefined _Boundary:_ scopes and uses spec sections to validate changes.
  • TDD-Driven Implementation: Follows RED–GREEN–REFACTOR cycles with tests for each task.
  • Structured Validation & Review: Requires implementer and reviewer prompts and structured status blocks for go/no-go decisions.

Quick Start

Run kiro-impl to autonomously process all pending tasks, or supply task numbers to execute a subset.

Frequently Asked Questions about kiro-impl

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

FAQPage Schema
How do I automate task solving in my repository using TDD subagents?

Autonomous task solving via TDD subagents is achieved by dispatching isolated subagents that follow strict RED–GREEN–REFACTOR cycles to complete predefined scope tasks. The kiro-impl skill coordinates these subagents to independently implement, validate, and commit tasks within repository boundaries.

What is the TDD workflow for autonomous task management and code review?

The TDD workflow for autonomous task management requires subagents to write failing tests first, implement code to pass tests, and then refactor. The kiro-impl skill enforces this RED–GREEN–REFACTOR discipline alongside structured implementer and reviewer prompts to ensure validated, traceable code commits.

How do I run a subset of pending tasks instead of processing all tasks autonomously?

To run a subset of pending tasks, supply specific task numbers to the kiro-impl skill instead of running it without arguments. This executes only the selected tasks in the main context while maintaining the same TDD validation and structured status block requirements.

Does kiro-impl work with predefined task boundaries in a SKILL scope?

Yes, kiro-impl operates strictly within predefined _Boundary:_ scopes in a repository's SKILL scope. It uses spec sections to validate changes, ensuring modular execution and controlled commits that satisfy boundary management and traceable validation requirements.

Can I execute selected tasks manually instead of dispatching autonomous subagents?

Yes, you can execute selected tasks manually in the main context using kiro-impl's manual mode. This mode processes specified tasks directly without dispatching autonomous subagents, while still applying strict TDD discipline and structured validation for go or no-go decisions.

Why does autonomous task implementation require structured status blocks for code review?

Structured status blocks are required for autonomous task implementation to enforce go or no-go decisions during code review. The kiro-impl skill uses these status blocks alongside implementer and reviewer prompts to ensure traceable validation and controlled commits before changes are approved.