Supported AI Agents Reference

Spec Kitty currently exposes 17 agent surfaces: 13 slash-command or prompt-file hosts and 4 project-local command-skill hosts.

Slash-command agents get user-global command directories such as ~/.claude/commands/ or ~/.opencode/command/. Codex CLI, Vibe, Pi, and Letta Code use shared project-local Agent Skills under .agents/skills/spec-kitty.<command>/.

Agent Overview

Slash-command and prompt-file agents

Agent	Global Directory	Commands Subdirectory	Slash Commands
Claude Code	`~/.claude/`	`commands/`	`/spec-kitty.*`
GitHub Copilot	`~/.github/`	`prompts/`	`/spec-kitty.*`
Google Gemini	`~/.gemini/`	`commands/`	`/spec-kitty.*`
Cursor	`~/.cursor/`	`commands/`	`/spec-kitty.*`
Qwen Code	`~/.qwen/`	`commands/`	`/spec-kitty.*`
OpenCode	`~/.opencode/`	`command/`	`/spec-kitty.*`
Windsurf	`~/.windsurf/`	`workflows/`	`/spec-kitty.*`
Google Antigravity	`~/.agent/`	`workflows/`	`/spec-kitty.*`
Kilocode	`~/.kilocode/`	`workflows/`	`/spec-kitty.*`
Augment Code	`~/.augment/`	`commands/`	`/spec-kitty.*`
Roo Cline	`~/.roo/`	`commands/`	`/spec-kitty.*`
Amazon Q (legacy)	`~/.amazonq/`	`prompts/`	`/spec-kitty.*`
Kiro	`~/.kiro/`	`prompts/`	`/spec-kitty.*`

Command-skill agents

Agent	Agent Key	Project Directory	Invocation Form
Codex CLI	`codex`	`.agents/skills/spec-kitty.<command>/`	`$spec-kitty.<command>`
Mistral Vibe	`vibe`	`.agents/skills/spec-kitty.<command>/` via `.vibe/config.toml`	Host skill syntax
Pi	`pi`	`.agents/skills/spec-kitty.<command>/`	`/skill:spec-kitty.<command>`
Letta Code	`letta`	`.agents/skills/spec-kitty.<command>/`	`/spec-kitty.<command>`

Command-skill packages share the same SKILL.md files. .kittify/command-skills-manifest.json records which configured agents own each package so removing one agent does not delete skills still used by another agent.

Managing Active Agents

Spec-kitty supports 17 AI agents (listed above). You can activate or deactivate agents at any time using the spec-kitty agent config command family.

To manage which agents are active in your project:

View configured agents: spec-kitty agent config list
Add agents: spec-kitty agent config add <agents>
Remove agents: spec-kitty agent config remove <agents>

See Managing AI Agents for complete documentation on agent management workflows.

For per-harness usage guides, see Codex, Pi TUI, and Letta Code.

Agent Details

Claude Code

Primary supported agent — Full feature support and extensive testing.

Property	Value
Directory	`.claude/`
Commands subdirectory	`commands/`
CLI flag	`--ai claude`
Status	Fully supported

Features:

Full slash command support
Custom command arguments
Project-level CLAUDE.md integration
Best documentation and testing coverage

Usage:

spec-kitty init my-project --ai claude
cd my-project
claude  # Launch Claude Code
/spec-kitty.specify Add user authentication

GitHub Copilot

Property	Value
Directory	`.github/`
Commands subdirectory	`prompts/`
CLI flag	`--ai copilot`
Status	Supported

Usage:

spec-kitty init my-project --ai copilot

Google Gemini

Property	Value
Directory	`.gemini/`
Commands subdirectory	`commands/`
CLI flag	`--ai gemini`
Status	Supported

Usage:

spec-kitty init my-project --ai gemini

Cursor

Property	Value
Directory	`.cursor/`
Commands subdirectory	`commands/`
CLI flag	`--ai cursor`
Status	Supported

Usage:

spec-kitty init my-project --ai cursor

Qwen Code

Property	Value
Directory	`.qwen/`
Commands subdirectory	`commands/`
CLI flag	`--ai qwen`
Status	Supported

Usage:

spec-kitty init my-project --ai qwen

OpenCode

Property	Value
Directory	`.opencode/`
Commands subdirectory	`command/` (note: singular)
CLI flag	`--ai opencode`
Status	Supported

Note: OpenCode uses command/ (singular) instead of commands/ (plural).

Usage:

spec-kitty init my-project --ai opencode

Windsurf

Property	Value
Directory	`.windsurf/`
Commands subdirectory	`workflows/`
CLI flag	`--ai windsurf`
Status	Supported

Note: Windsurf uses workflows/ instead of commands/.

Usage:

spec-kitty init my-project --ai windsurf

GitHub Codex

Property	Value
Directory	`.agents/skills/`
Commands subdirectory	`spec-kitty.<command>/SKILL.md`
CLI flag	`--ai codex`
Status	Supported

Codex uses project-local Agent Skills. Spec Kitty installs one SKILL.md package per command under .agents/skills/spec-kitty.<command>/.

Usage:

spec-kitty init my-project --ai codex

Kilocode

Property	Value
Directory	`.kilocode/`
Commands subdirectory	`workflows/`
CLI flag	`--ai kilocode`
Status	Supported

Note: Kilocode uses workflows/ instead of commands/.

Usage:

spec-kitty init my-project --ai kilocode

Augment Code

Property	Value
Directory	`.augment/`
Commands subdirectory	`commands/`
CLI flag	`--ai auggie`
Status	Supported

Usage:

spec-kitty init my-project --ai auggie

Roo Cline

Property	Value
Directory	`.roo/`
Commands subdirectory	`commands/`
CLI flag	`--ai roo`
Status	Supported

Usage:

spec-kitty init my-project --ai roo

Amazon Q (legacy)

Property	Value
Directory	`.amazonq/`
Commands subdirectory	`prompts/`
CLI flag	`--ai q`
Status	Legacy — rebranded to Kiro

Amazon Q Developer CLI has been rebranded to Kiro CLI. Existing projects using --ai q continue to work; new projects should select --ai kiro. The Kiro installer automatically copies ~/.aws/amazonq/ to ~/.kiro/ at the user level.

Usage:

spec-kitty init my-project --ai q  # legacy

Kiro

Property	Value
Directory	`.kiro/`
Commands subdirectory	`prompts/`
CLI flag	`--ai kiro`
Binary	`kiro-cli`
Status	Supported

Kiro CLI (formerly Amazon Q Developer CLI) supports slash-command arguments via $ARGUMENTS, but the full invocation must be shell-quoted for arguments to pass through. See kirodotdev/Kiro#4141.

# Correct — arguments reach $ARGUMENTS
kiro '@speckit.specify my feature description'

# Incorrect — arguments are swallowed
kiro @speckit.specify my feature description

Usage:

spec-kitty init my-project --ai kiro

Multi-Agent Setup

You can initialize a project with multiple agents:

# Initialize with Claude and Pi
spec-kitty init my-project --ai claude,pi

# Initialize with all agents
spec-kitty init my-project --ai claude,copilot,gemini,cursor,qwen,opencode,windsurf,codex,kilocode,auggie,roo,q,kiro,antigravity,vibe,pi,letta

This registers all specified agents, allowing team members to use their preferred tool. Slash-command files are installed in user-global agent roots at CLI startup; Codex, Vibe, Pi, and Letta command skills are installed project-locally under .agents/skills/.

Adding Agents Later

To add agent support to an existing project:

spec-kitty agent config add pi letta

For project configuration, use spec-kitty agent config add <agent> rather than manually copying command files. After upgrading an older project, spec-kitty upgrade refreshes missing .pi/, .letta/, and .agents/skills/ backfill state for configured Pi and Letta projects.

Slash Commands

All agents support the same 13 slash commands:

Command	Purpose
`/spec-kitty.specify`	Create feature specification
`/spec-kitty.plan`	Create implementation plan
`/spec-kitty.tasks`	Generate work packages
`/spec-kitty.implement`	Start WP implementation
`/spec-kitty.review`	Review completed work
`/spec-kitty.accept`	Validate an approved mission before merge
`/spec-kitty.merge`	Merge an accepted mission to its target branch
`/spec-kitty.status`	Show kanban status
`/spec-kitty.dashboard`	Open web dashboard
`/spec-kitty.charter`	Create project principles
`/spec-kitty.research`	Conduct research
`/spec-kitty.analyze`	Analyze codebase

See Slash Commands for complete documentation.

Command-skill hosts use the same Spec Kitty workflow commands but expose them through their host-specific skill invocation syntax. See Supported Harnesses for current tier status and per-harness links.

Agent Selection Guidelines

Scenario	Recommended Agent
Best overall experience	Claude Code
VS Code integration	Cursor, GitHub Copilot
JetBrains IDEs	Cursor
AWS environment	Kiro (formerly Amazon Q)
Open source preference	OpenCode, Qwen
Enterprise/air-gapped	Any (local templates available)

Troubleshooting

Slash commands not appearing

Verify the global agent directory exists:
```
ls -la ~/.claude/commands/
```
Regenerate commands:
```
spec-kitty upgrade
```
Restart your AI agent

Agent-specific issues

Kiro / Amazon Q: Slash-command arguments only pass through when the full invocation is shell-quoted (e.g. kiro '@speckit.specify <description>'). Without quoting, the trailing text is not forwarded to $ARGUMENTS. See kirodotdev/Kiro#4141.

Codex: Confirm project-local Agent Skills exist:

ls .agents/skills/spec-kitty.specify/SKILL.md
spec-kitty agent config sync

Table of Contents

Supported AI Agents Reference

Agent Overview

Slash-command and prompt-file agents

Command-skill agents

Managing Active Agents

Agent Details

Claude Code

GitHub Copilot

Google Gemini

Cursor

Qwen Code

OpenCode

Windsurf

GitHub Codex

Kilocode

Augment Code

Roo Cline

Amazon Q (legacy)

Kiro

Multi-Agent Setup

Adding Agents Later

Slash Commands

Agent Selection Guidelines

Troubleshooting

Slash commands not appearing

Agent-specific issues

See Also

Getting Started

Practical Usage

Background