kiro-impl-fast

Implements low-risk spec tasks sequentially with a single end-of-run build, test, and review gate.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/scapia-oss/compass --skill kiro-impl-fast-scapia-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-impl-fast
Source: https://github.com/scapia-oss/compass/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-impl-fast
Command: npx skills add https://github.com/scapia-oss/compass --skill kiro-impl-fast-scapia-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Standard per-task implementation workflows run build, test, and review after every task, which is wasteful for small, low-risk changes — especially on slow build stacks like Gradle. This Skill implements simple spec tasks in one sequential pass and runs verification exactly once at the end. ## Core Features & Use Cases - Batched implementation: Writes all selected tasks in a single pass (Sonnet writer subagent by default, Opus optional) without TDD red/green cycles or per-task review. - Single end gate: Runs build/tests, an inline review, and completion verification once over the cumulative diff, with bounded repair rounds (3 for build, 2 for review). - Direct mode: --direct "<change>" handles spec-less cosmetic edits (styling, typos, config values) with hard guards that refuse behavioral or redline changes and route them to spec capture. - Use Case: Adding a DTO field or bumping a dependency across three approved tasks in a Gradle repo — instead of three slow build cycles, the Skill writes all changes, then builds, reviews, verifies, and commits once. ## Quick Start Ask the AI to run kiro-impl-fast for your feature, e.g. "implement the pending tasks for my-feature with kiro-impl-fast".

Frequently Asked Questions about kiro-impl-fast

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

FAQPage Schema
How do I implement simple spec tasks without per-task builds?

Run kiro-impl-fast with the feature name and optional task numbers. It writes all selected tasks in one pass, then runs build, tests, review, and completion verification exactly once at the end before committing.

When should I use kiro-impl-fast vs kiro-impl?

Use kiro-impl-fast for small, low-risk, non-behavioral work like config entries, DTO additions, copy changes, and dependency bumps. Use kiro-impl for behavioral, cross-boundary, money/auth/IO-critical, or large task sets where per-task verification localizes failures.

Can I make a quick cosmetic change without creating a spec?

Yes, use --direct "<change>" for cosmetic-only edits such as styling, typos, static text, or single-file config values. Behavioral or redline changes are refused and routed to spec capture via kiro-spec-quick.

Does kiro-impl-fast skip tests entirely?

No. It skips the TDD red/green cycle and per-task test runs, but the end gate always runs the build and test commands once. The --no-tests flag only skips writing new tests, never the verification gate.

What happens if the end-of-run build fails?

The Skill attempts bounded repair — up to 3 rounds for build/test failures and 2 for review findings, optionally dispatching a debug subagent. If still failing, it stops, reports remaining failures, and leaves affected tasks unmarked.

Can I leave changes uncommitted instead of per-task commits?

Yes. Pass --no-commit or set commit_policy to leave-uncommitted in spec.json. The Skill then makes no commits or staging, ticks tasks.md, and hands you the working tree to stage and commit yourself.