Getting Started

Set up Claude Kiro in your project and create your first specification in minutes.

Prerequisites

Before you begin, make sure you have:

  • Claude Code - The official Claude CLI from Anthropic
  • uv - Python package installer ( docs.astral.sh/uv )
  • A project directory where you want to use spec-driven development

Installation

Install Claude Kiro using uv :

uv tool install claude-kiro

Verify installation:

ck --version

Initialize Your Project

Navigate to your project directory and run:

ck init

This command creates:

  • .claude/ - Configuration directory
  • .claude/commands/spec/ - Slash commands (create, implement, review)
  • .claude/output-styles/ - Spec-driven output style
  • .claude/specs/ - Your specifications will go here
  • .claude/CLAUDE.md - Project-specific instructions for Claude
What's happening? The ck init command sets up the Claude Code configuration that enables spec-driven development. It adds slash commands, configures the output style, and creates the directory structure for your specifications.

Verify Setup

Check that everything is configured correctly:

ck doctor

This command validates:

  • Claude Code configuration exists
  • All required directories are present
  • Slash commands are properly configured
  • Output style is active

Create Your First Spec

Open Claude Code in your project and run:

/spec:create user-authentication

Claude will guide you through a 3-phase workflow:

Phase 1: Requirements

Claude generates requirements.md with EARS notation requirements. You'll review and approve before proceeding.

Phase 2: Design

Claude creates design.md with architecture, data models, and testing strategy. Another review/approval checkpoint.

Phase 3: Tasks

Claude generates tasks.md with specific implementation tasks. Once approved, you're ready to implement!

Implement Tasks

Once your spec is complete, implement tasks with:

/spec:implement .claude/specs/user-authentication

Claude will:

  • Load the spec context (requirements, design, tasks)
  • Guide implementation with TodoWrite tracking
  • Follow test-driven development practices
  • Verify acceptance criteria before marking complete

What's Next?

📖 Learn the Methodology

Understand the spec-driven workflow and why it works.

Read Methodology

⚙️ CLI Reference

Explore all ck commands and options.

View CLI Docs

💡 See Examples

Learn from real-world spec examples and patterns.

View Examples

Troubleshooting

Command Not Found: ck

If ck isn't recognized, ensure uv's bin directory is in your PATH: 

# Add to your shell profile (~/.bashrc, ~/.zshrc, etc.)
export PATH="$HOME/.local/bin:$PATH"

Slash Commands Not Working

Make sure you're running ck init from your project root. Slash commands require the .claude/commands/ directory structure.

Spec Not Loading

Check that your spec path is correct and contains all three files: 

.claude/specs/your-spec/
├── requirements.md
├── design.md
└── tasks.md

Need More Help?

Report issues or ask questions on GitHub Issues .