Integrations
Integrations connect Spec Kit to your AI coding agent through commands, skills, or recipes. Use none for shared scaffolding without an agent. Choose an integration below for prerequisites, setup, invocation syntax, and integration-specific options or limitations.
Set Up Your Agent
See the installation guide for CLI prerequisites and installation, and the SDD quickstart for your first process.
For a new project:
specify init my-project --integration <key>
Invoke process commands inside your coding agent, not in the terminal.
The documentation commonly uses /speckit.* notation, but your agent may use
hyphenated skills, $ skills, or another native form. See your integration's
page and the command invocation comparison.
Adding Another Agent
In an initialized project, use
specify integration install <key>.
Check the agent's guide for its multi-install safety status and follow the
shared multi-install rules.
Installing another integration does not change the default. Use
specify integration use <key>
to activate it.
Removing an Agent
Use specify integration uninstall <key>
to remove an agent's Spec Kit integration, not the agent application itself.
See the uninstall reference for modified-file handling and cleanup exceptions.
To replace an integration instead, use
specify integration switch <key>.
Working in a Team
Mixed-agent teams can start from an agent-neutral project:
specify init my-project --integration none
Each developer switches to their chosen agent in their local checkout:
specify integration switch <key>
After development, switch back before staging the commit:
specify integration switch none
Important
Do not manually edit Spec Kit-generated agent commands or skills. Maintain
customizations in reviewed presets or
project-local overrides.
Before committing, use
specify integration status to verify
that none is the only installed and default integration. Review the Git diff
and any retained agent files.
Teams can add CI checks for the committed baseline and optional pre-commit checks of staged files.
Choose an Integration
Use the exact key shown below with --integration <key>. CLI-based integrations
require the agent's CLI to be installed; IDE-based integrations run through the
agent's chat window in your IDE. Each page links to the agent's installation documentation.
| Integration | Key |
|---|---|
| Alquimia AI | alquimia |
| Amp | amp |
| Antigravity | agy |
| Auggie CLI | auggie |
| Claude Code | claude |
| Cline | cline |
| CodeBuddy CLI | codebuddy |
| Codex CLI | codex |
| Command Code | command-code |
| Cursor | cursor-agent |
| DeepSeek Harness | dsh |
| Devin for Terminal | devin |
| Docker Agent | docker-agent |
| Factory Droid | droid |
| Firebender | firebender |
| Forge | forge |
| Gemini CLI | gemini |
| GitHub Copilot | copilot |
| Goose | goose |
| Grok Build | grok |
| Hermes | hermes |
| IBM Bob | bob |
| Junie | junie |
| Kilo Code | kilocode |
| Kimi Code | kimi |
| Kiro CLI | kiro-cli |
| Lingma | lingma |
| MiniMax Code | mcode |
| Mistral Vibe | vibe |
| Muse Code | muse |
| None: shared scaffolding only | none |
| Oh My Pi | omp |
| opencode | opencode |
| Pi Coding Agent | pi |
| Qoder CLI | qodercli |
| Qwen Code | qwen |
| RovoDev | rovodev |
| SHAI (OVHcloud) | shai |
| Tabnine CLI | tabnine |
| Trae | trae |
| ZCode | zcode |
| Zed | zed |
| Generic: bring your own agent | generic |
Shared Management and External Integrations
The integration CLI reference documents shared installation, upgrade, removal, status, catalogs, and default-selection behavior. Those rules apply across integrations rather than being repeated on each page. The individual guides also identify whether workflow CLI dispatch is supported; an IDE setup that needs no CLI does not imply that workflow steps can run without one.
For agents not listed here, use the generic integration or discover an external adapter. Review external adapter code before authorizing its execution. Catalog discovery is not a security endorsement; the default community catalog is discovery-only. See catalog-installed external adapters for trust and installation requirements.
The catalog reference describes descriptor and catalog metadata. See contributing integrations to develop a built-in integration or publish an external adapter.