kiro-impl

Dispatch specialized subagents to implement tasks with TDD discipline.

Updated Feb 25, 2024
One-click install
npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-impl-ryowatanabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-impl
Source: https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper/tree/main/.claude/skills/kiro-impl
Command: npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-impl-ryowatanabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes the execution of approved tasks by orchestrating a dedicated subagent for each task, enabling disciplined, test-driven development and traceable progress across autonomous and manual modes.

Core Features & Use Cases

  • Autonomous mode: Dispatch an independent subagent per task to work to completion with after-action review.
  • Manual mode: Execute selected tasks directly in the main context when task numbers are provided.
  • Rigorous governance: Enforces structured status blocks, reviewer checks, and selective commits to maintain a clean history and reproducible validation.

Quick Start

Command a new subagent to tackle a pending task, then verify the results with the prescribed review and commit flow.

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-driven development with subagent orchestration?

Task-driven subagent orchestration automates end-to-end implementation by dispatching specialized subagents per task with TDD discipline. It operates in autonomous mode for full completion or manual mode when specific task numbers are provided.

What is the difference between autonomous mode and manual mode for task execution?

Autonomous mode dispatches an independent subagent per task to work to completion with after-action review. Manual mode executes selected tasks directly in the main context when specific task numbers are provided.

How do I enforce TDD discipline and traceable commits across automated tasks?

TDD discipline and traceable commits are enforced through structured status blocks, bounded reviewer checks, and selective commits. This governance maintains clean history and ensures reproducible validation across dispatched subagents.

Can I execute specific task numbers directly instead of running the full autonomous workflow?

Yes, manual mode executes specific task numbers directly in the main context rather than dispatching independent subagents. It still adheres to boundary constraints, status parsing, and prescribed validation commands.

What spec sources and boundary constraints are needed for subagent task automation?

Subagent task automation reads spec sources to understand requirements and adheres to boundary constraints to limit scope. It enforces strict status parsing and bounded reviews to ensure alignment with prescribed validation commands.

Why use bounded reviews and selective commits in a TDD subagent workflow?

Bounded reviews and selective commits in a TDD subagent workflow ensure traceable progress and alignment with validation commands. This governance maintains a clean, reproducible commit history across all executed tasks.