spec-impl

A command for implementing tasks from a software specification using test-driven development (TDD), a method where tests are written before the code.

In plain words
What is it for?
Use it to execute all pending tasks, or selected task numbers, from a Kiro specification.
Why use it?
It turns documented requirements and design into an ordered implementation process and checks each change with tests.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/kbwo/ccmanager/spec-impl
Clone the repo
git clone --depth 1 https://github.com/kbwo/ccmanager

Made for: Claude Code.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 555 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00007 $0.00555
Opus 5 $0.00003 $0.00278
Sonnet 5 $0.00001 $0.00111
Haiku 4.5 $0.00001 $0.00056

Measured yesterday against content hash db78888ac8d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-impl scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/kiro/spec-impl.md · 62 lines

What it actually says

Execute Spec Tasks with TDD

Execute implementation tasks for $1 using Kent Beck's Test-Driven Development methodology.

Instructions

Pre-Execution Validation

Validate required files exist for feature $1:

  • Requirements: .kiro/specs/$1/requirements.md
  • Design: .kiro/specs/$1/design.md
  • Tasks: .kiro/specs/$1/tasks.md
  • Metadata: .kiro/specs/$1/spec.json

Context Loading

Core Steering:

  • Structure: @.kiro/steering/structure.md
  • Tech Stack: @.kiro/steering/tech.md
  • Product: @.kiro/steering/product.md

Custom Steering:

  • Additional *.md files in .kiro/steering/ (excluding structure.md, tech.md, product.md)

Spec Documents for $1:

  • Metadata: @.kiro/specs/$1/spec.json
  • Requirements: @.kiro/specs/$1/requirements.md
  • Design: @.kiro/specs/$1/design.md
  • Tasks: @.kiro/specs/$1/tasks.md

Task Execution

  1. Feature: $1
  2. Task numbers: $2 (optional, defaults to all pending tasks)
  3. Load all context (steering + spec documents)
  4. Execute selected tasks using TDD methodology

TDD Implementation

For each selected task:

  1. RED: Write failing tests first
  2. GREEN: Write minimal code to pass tests
  3. REFACTOR: Clean up and improve code structure
  4. Verify:
    • All tests pass
    • No regressions in existing tests
    • Code quality and test coverage maintained
  5. Mark Complete: Update checkbox from - [ ] to - [x] in tasks.md

Note: Follow Kent Beck's TDD methodology strictly, implementing only the specific task requirements.

Implementation Notes

  • Feature: Use $1 for feature name
  • Tasks: Use $2 for specific task numbers (optional)
  • Validation: Check all required spec files exist
  • TDD Focus: Always write tests before implementation
  • Task Tracking: Update checkboxes in tasks.md as completed
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 62 lines · 7 tokens per session scan A db78888ac8d0

Subscribe to this mod's changes

spec-impl is a command published in the GitHub repository kbwo/ccmanager (1,229 stars, last pushed yesterday), licensed MIT. It adds 7 tokens to every session and 555 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.