kiro-impl

Implement approved tasks from tasks.md using autonomous sub-agent dispatch or manual execution.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-impl-shimamatz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-impl
Source: https://github.com/shimaMatz/driver-copilot/tree/main/.cursor/skills/kiro-impl
Command: npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-impl-shimamatz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orients teams to build and manage tasks using a controlled multi-agent AI flow, reducing manual orchestration by dispatching sub-agents to implement tasks via TDD.

Core Features & Use Cases

  • Autonomous task execution: runs pending tasks using a dispatch workflow with sub-agents.
  • Manual task selection: executes specific tasks provided by users in the main context.
  • Auditability: tracks progress and decisions in tasks.md, with explicit commit messages and boundaries.

Quick Start

Execute the kiro-impl skill to begin processing the next pending task.

Frequently Asked Questions about kiro-impl

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

FAQPage Schema
How do I automate TDD task implementation using sub-agents?

Autonomous TDD task implementation is automated by dispatching sub-agents to execute pending tasks defined in tasks.md. The workflow validates completion criteria using parent-provided tests, builds, and smoke commands to ensure auditable progress tracking.

What is a KIRO-like workflow for multi-agent task orchestration?

A KIRO-like workflow is a two-mode process that coordinates multi-agent AI flow to reduce manual orchestration. It operates in either autonomous sub-agent dispatch or manual execution mode, enforcing strict auditable processes with status tracking documented in tasks.md.

Do I need requirements.md and design.md files to run TDD workflow automation?

Yes, TDD workflow automation requires projects to have tasks defined in tasks.md with linked spec sections in requirements.md and design.md. These files provide the approved task definitions and design specifications needed for sub-agent dispatch and validation.

Can I manually select specific tasks for sub-agent execution instead of running all pending tasks?

Yes, you can manually select specific tasks for execution by providing them in the main context. The workflow supports a manual task selection mode that runs specific user-provided tasks instead of automatically processing the next pending task.

How does autonomous task execution track progress and ensure auditability?

Autonomous task execution tracks progress and ensures auditability by documenting decisions and status in tasks.md with explicit commit messages and boundaries. This enforces strict process validation against parent-provided tests and smoke commands.

What are the limitations of using sub-agent dispatch for TDD task implementation?

Sub-agent dispatch for TDD task implementation is limited to projects with tasks already defined in tasks.md and linked specifications in requirements.md and design.md. It requires parent-provided tests, builds, and smoke commands to validate completion criteria.