A help command for Kiro, a software-development workflow that turns a feature idea into requirements, design, tasks, and implementation steps.

Use it to understand Kiro phases such as project setup, specification writing, requirements, design, task planning, and implementation.

It explains the workflow and its commands so developers know what to do before and during coding. This gives a project a documented plan instead of starting with code alone.

How reinhardhq/claude-code-spec-boilerplate configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to reinhardhq/claude-code-spec-boilerplate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/reinhardhq/claude-code-spec-boilerplate/main/.claude/commands/kiro:help.md

Clone the repo

git clone --depth 1 https://github.com/reinhardhq/claude-code-spec-boilerplate

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-help/github.svg)](https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-help)

Your own site

<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-help"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-help/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-help"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-help.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,401 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.01401
Opus 5.5	$0.00004	$0.00560
Sonnet 5.5	$0.00002	$0.00280
Haiku 4.5	$0.00001	$0.00140

Measured 2mo ago against content hash ab1fb0be46ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

kiro:help 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 2mo ago.

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:help.md · 197 lines

How it starts

The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Kiro Help - Spec-Driven Development Workflow

This command provides comprehensive guidance on using the Kiro specification-driven development system.

What is Kiro?

Kiro is a specification-driven development framework that helps you build software features through a systematic, phase-based approach. It ensures proper documentation, planning, and review before implementation begins.

Workflow Overview

The Kiro workflow follows these phases in order:

graph TD
    A[Phase 0: Steering<br>/kiro:steering] -->|Optional| B[Phase 1: Initialize Project<br>/kiro:init]
    B --> C[Phase 2: Create Spec<br>/kiro:spec-init]
    C --> D[Phase 3: Generate Requirements<br>/kiro:spec-requirements]
    D --> E[Phase 4: Create Design<br>/kiro:spec-design]
    E --> F[Phase 5: Plan Tasks<br>/kiro:spec-tasks]
    F --> G[Phase 6: Implementation<br>Start coding!]
    
    style A fill:#e1f5fe
    style G fill:#c8e6c9

Command Reference

Phase 0: Steering (Optional)

Commands:

/kiro:steering - Create/update standard steering documents
/kiro:steering-custom - Create custom steering for specialized contexts

Purpose: Establish project context and constraints. Optional for new features or small additions.

Creates:

.kiro/steering/product.md - Product overview and business context
.kiro/steering/tech.md - Technology stack and development environment
.kiro/steering/structure.md - Project structure and architectural patterns

Phase 1: Project Initialization

Command: /kiro:init

Purpose: Initialize the Kiro system in your project with example specifications.

Creates:

.kiro/ directory structure
Example specifications for learning
Initial project setup

Phase 2: Specification Initialization

Command: /kiro:spec-init [detailed description]

Purpose: Initialize a new feature specification based on your detailed project description.

Example:

/kiro:spec-init Create a user authentication system with email/password login, JWT tokens, password reset functionality, and role-based access control

Read the full file on GitHub · 197 lines

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.

2mo ago First seen · 197 lines · 11 tokens per session scan A ab1fb0be46ea

Subscribe to this mod's changes

kiro:help is a command published in the GitHub repository reinhardhq/claude-code-spec-boilerplate (2 stars, last pushed 1y ago), licensed MIT. It adds 11 tokens to every session and 1,401 once invoked, about $0.0000 per session on Opus 5.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-31.

Planning

kiro:help next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
kiro:helpreinhardhq/claude-code-spec-boilerplate	Command	2	1y ago	MIT	A	11	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

claude-code-spec-boilerplate: Command for Claude Code