kiro-cli

Delegate multi-step codebase tasks to Kiro CLI in isolated subagent sessions.

5|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/amirkiarafiei/subagent-cli-skills --skill kiro-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-cli
Source: https://github.com/amirkiarafiei/subagent-cli-skills/tree/main/skills/kiro-cli
Command: npx skills add https://github.com/amirkiarafiei/subagent-cli-skills --skill kiro-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It reduces the cost and context load of doing large, multi-step codebase edits and investigations by delegating the tactical execution to Kiro CLI while you stay the orchestrator.

Core Features & Use Cases

  • Subagent-style delegation: Runs a separate long-horizon pass for heavy exploration, refactors, and batch edits.
  • Context handoff for alignment: Prompts include the original goal, prior decisions, scope, constraints, and verification steps to keep isolated sessions consistent with the main thread.
  • Programmatic, non-interactive execution: Uses Kiro CLI in chat mode with trust-all-tools to enable reliable automated task runs.

Quick Start

Ask an AI assistant to delegate a bounded, multi-step implementation request to the Kiro CLI skill while specifying the repo scope, key decisions already made, constraints, and an explicit verification command to run before returning results.

Frequently Asked Questions about kiro-cli

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

FAQPage Schema
How do I delegate large codebase refactoring without consuming too much main agent context?

You can delegate large codebase refactoring by running an isolated subagent session via Kiro CLI, handing off context like goals and constraints to execute heavy edits without loading the main agent context.

What is the best way to automate batch file writes across specified repository paths?

Automating batch file writes is best handled by delegating the tactical execution to a non-interactive Kiro CLI session, which processes multi-step edits across specified repo paths using trust-all-tools.

Do I need a non-interactive environment to run deep codebase exploration with Kiro CLI?

Yes, deep codebase exploration requires non-interactive Kiro CLI execution using chat --no-interactive with trust-all-tools and a selected model to ensure reliable automated task runs.

How does context handoff work when delegating multi-step code edits to a subagent?

Context handoff works by passing a shared-state prompt containing the original goal, prior decisions, scope, constraints, and verification steps to keep the isolated subagent session aligned with the main orchestration thread.

When should I not use an isolated subagent for repo work?

You should avoid using an isolated subagent for repo work when the task lacks explicit scope, defined constraints, or a clear verification command, as the delegated session requires these to execute reliably.