lockstep
4 min readNaman Jain

Kiro vs Claude Code: specs, steering, and how they compare

Kiro vs Claude Code from their own docs: Kiro's specs and steering vs CLAUDE.md and skills, surfaces, models, hooks, and which fits spec-first work.

A developer tries Kiro for a new feature and likes that it writes requirements, then a design, then tasks, and waits for approval at each step. Back in their main repository, the team uses Claude Code with a long CLAUDE.md. They want to know whether to switch, or bring the spec habit over.

This guide compares the two from their own documentation: Kiro's docs and Claude Code's, checked on 16 November 2026. It leaves out pricing and benchmark scores.

The short answer

KiroClaude Code
Core ideaSpec-driven development built inGeneral agent you configure
SurfacesIDE, CLI, web, iOS; ACP editors such as JetBrains and ZedTerminal, VS Code, JetBrains, desktop app, web, mobile
Standing contextSteering files in .kiro/steering/; AGENTS.mdCLAUDE.md, .claude/rules/
Feature planningSpecs: requirements.md, design.md, tasks.mdPlan mode; Spec Kit as an add-on
ModelsSeveral providers, plus Auto routingClaude
HooksYesYes
MCPYesYes
Custom agentsYesSubagents
Cloud workSessions keep running in the cloudCloud sessions

Kiro's specs

Specs are Kiro's center. Each one lives in .kiro/specs/<feature>/ with three files:

  • requirements.md: user stories and acceptance criteria (or bugfix.md for bug fixes, with current, expected, and unchanged behavior)
  • design.md: architecture, sequence diagrams, and implementation considerations
  • tasks.md: discrete, trackable implementation tasks

Kiro's docs list variants: feature specs with requirements-first or design-first workflows, bugfix specs, a Quick Spec that generates all three in one pass without approval gates, a plan mode, requirements analysis that looks for gaps and contradictions, and in the IDE, property-based tests to check correctness.

Kiro's steering

Steering files give Kiro persistent context. Workspace files live in .kiro/steering/, global ones in ~/.kiro/steering/, and workspace wins on conflict. The default foundation files are product.md (purpose and users), tech.md (stack and constraints), and structure.md (layout and conventions), included in every interaction. Kiro also reads AGENTS.md, and its docs describe pushing team steering files to machines through MDM.

Kiro's harness

Kiro's docs describe one agent harness behind every surface, which clients reach over the open Agent Client Protocol (ACP). Each turn assembles context from steering and attachments, runs the model, checks every tool call against permission rules, runs tools, and compacts history near the context limit, with hooks at stages such as prompt submit, pre tool use, and agent stop. See what an AI coding agent harness is.

Where Claude Code differs

  • Configuration depth for teams. CLAUDE.md, skills, hooks, permission modes including auto mode, and managed settings that let an organization enforce policy.
  • Scaling work. Subagents, experimental agent teams, and dynamic workflows.
  • Specs are optional. Use plan mode for a plan before edits, or Spec Kit with Claude Code for a requirements, plan, and tasks flow similar to Kiro's.
  • Claude models only, where Kiro lists models from several providers and an Auto router.

Mapping concepts

KiroClaude Code equivalent
Steering fileCLAUDE.md or a file in .claude/rules/
SpecSpec Kit spec, or a plan file you commit
HookHook in settings.json
Custom agentSubagent in .claude/agents/
Power or MCP serverPlugin or MCP server

Moving between them is mostly copying markdown: steering content into CLAUDE.md or AGENTS.md (which both read), and specs into the repository where either agent can read them.

Which to choose

  • You want spec-driven development without assembling it: Kiro.
  • You want model choice in one tool: Kiro.
  • You already run Claude Code, or need organization-wide policy and many surfaces: Claude Code, with Spec Kit if you want specs.
  • Undecided: run the same feature through both, starting from the same requirements.

Where specs and steering stop

Steering files describe standing conventions. Specs capture a feature at the moment it was planned. Neither tracks the decision made two weeks later in a PR thread that changed the design. Kiro's own docs describe steering as capturing decisions as the project evolves, which works only if someone updates the file.

Where Lockstep fits

Lockstep captures decisions from PRDs, Slack, and pull requests, routes each to its owner for approval, and briefs Claude Code sessions on the ones that apply. Briefings, hooks, and managed skills are Claude Code features; Kiro and other MCP clients can call Lockstep's tools directly.

See how it works.

Sources checked 16 November 2026

For spec tools side by side, see Spec Kit vs Kiro vs OpenSpec vs BMAD. For other agents compared, see Cursor vs Antigravity vs Claude Code. For more on ACP, see MCP vs A2A vs ACP.

Frequently asked questions

What is Kiro?
An AI coding agent that Kiro's docs describe as one unified agent harness used from the Kiro IDE, Kiro CLI, web, and mobile, and from ACP-compatible editors such as JetBrains IDEs and Zed. Its signature feature is specs: structured requirements, design, and task files for each feature.
What is the difference between Kiro and Claude Code?
Kiro builds spec-driven development in: each feature gets requirements, design, and tasks files, with approval between phases. Claude Code is a general agent configured through CLAUDE.md, skills, and hooks; spec workflows are added with tools like Spec Kit or plan mode. Kiro also lets you choose among several model providers.
What are Kiro steering files?
Markdown files in .kiro/steering/ (workspace) or ~/.kiro/steering/ (global) that give Kiro persistent context: by default product.md, tech.md, and structure.md. They play the same role as CLAUDE.md in Claude Code. Kiro also supports AGENTS.md.
Does Kiro support hooks like Claude Code?
Yes. Kiro's docs describe event-driven hooks around its agent loop, including Prompt Submit, Pre Tool Use, and Agent Stop hooks. Claude Code has hooks at similar points. The configuration formats differ, so hooks don't transfer directly.
Can I use Kiro specs with Claude Code?
The files are markdown, so Claude Code can read them if you point it at .kiro/specs/<feature>/. For a structured spec workflow inside Claude Code, GitHub's Spec Kit installs specify, plan, tasks, and implement steps as Claude Code skills.

Keep reading