Loading image...Kiro
  • CLI
  • Web
  • Enterprise
  • Pricing
  • Docs
SIGN INDOWNLOADS
Loading image...Kiro
Loading image...Kiro
Product
  • About Kiro
  • CLI
  • Web
  • Pricing
  • Downloads
For
  • Enterprise
  • Startups
  • Students
Community
  • Overview
  • Ambassadors
  • Discord
  • Events
  • Powers
  • Shop
  • Showcase
Resources
  • Docs
  • Blog
  • Changelog
  • FAQs
  • Report a bug
  • Suggest an idea
  • Billing support
Social
Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences
  1. Docs
  2. CLI
  3. V3
  4. Specs

Specs in CLI


Overview

Specs bring structured, plan-then-execute development to the CLI. The Spec agent is a built-in agent that runs alongside your custom agents on the unified engine. Switch to it when you want the agent to think through requirements and design before writing code, then execute an implementation plan with verification between each task.

Because Spec is a standard agent, your permissions, hooks, and MCP servers all apply to it the same way they apply to any other agent.

Using specs

The /spec slash command manages spec workflows:

CommandWhat it does
/specList existing specs in the workspace and select one
/spec new <name>Start a new spec -- the agent switches to Spec mode and begins requirements
/spec <name>Resume an existing spec where you left off
/spec run <name>Execute all tasks in a spec's implementation plan autonomously

When you run /spec new or /spec <name>, the CLI switches to the Spec agent. When execution completes or you manually switch back, the agent returns to your previous mode.

Quick example

> /spec new auth-middleware Spec agent activated. Let me analyze your request and produce requirements... [Agent produces requirements.md with acceptance criteria] > Looks good, proceed to design. [Agent produces design.md with architecture decisions] > Execute the tasks. [Agent works through tasks.md sequentially, verifying between steps]

How specs work

  1. Requirements -- the agent analyzes your request and produces structured acceptance criteria
  2. Design -- technical design with architecture decisions and component breakdown
  3. Tasks -- an ordered implementation plan with dependency tracking
  4. Execution -- tasks run sequentially with verification between steps

Each phase produces a file in .kiro/specs/<name>/:

text
.kiro/specs/my-feature/ requirements.md design.md tasks.md

You can review and edit these files between phases. The agent respects your changes.

Running tasks

/spec run <name> validates that tasks.md exists, then triggers autonomous execution. The agent works through each task without further prompts, streaming progress as it goes. You can interrupt at any point.

Spec types

When you run /spec new, the agent asks what kind of spec you want:

  • Build a Feature -- structured requirements, design, and implementation tasks
  • Fix a Bug -- investigation, root cause analysis, and fix
  • Quick Spec -- lightweight planning without full requirements formalization

Portability

Specs are stored in .kiro/specs/ which is shared across all Kiro surfaces. Start a spec in the CLI, continue it in the IDE. The file format is identical.

Learn more

For the full specs reference, see the IDE documentation:

  • Feature Specs -- requirements-first and design-first workflows
  • Bugfix Specs -- bug investigation and fix workflows
Page updated: June 17, 2026
CLI 3.0 (Early Access)
Permissions