Skip to Content
OpenSpec
Reference

Supported tools

Which AI coding tools OpenSpec supports, and how to invoke each one's skills.

Every tool in the matrix runs the same OpenSpec workflows, installed as skills. Earlier versions also wrote command files. Upgrade to 2.0 covers what happens to them.

Where skills go

New projects use machine-wide skills by default. With --scope project, the installer writes to .agents/skills/ and gives tools that need their own folder a link or copy of each skill.

A project set up for Claude Code, Cursor, and Codex:

my-project/
├── .agents/skills/
│   ├── .openspec-target           the tools set up here, one per line
│   └── openspec-propose/SKILL.md  the one copy every tool reads
└── .claude/
    └── skills/openspec-propose    link to ../../.agents/skills/openspec-propose

Cursor and Codex read .agents/skills/ themselves, so they need nothing else.

Project installs leave skills-lock.json alone.

.openspec-target is how openspec update knows which tools are set up and what is OpenSpec's. Each line is one of:

LineMeaning
<tool>A tool set up in this project, such as cursor.
<tool> own-filesOpenSpec gave the tool links in its own folder, such as claude own-files. Delete that folder and update removes the tool.

Vercel’s skills package places the skills in the folders each agent reads. Windows project installs use copies. Run openspec init --help for the full list, including tools such as AiderDesk (aider-desk). Existing OpenSpec IDs still work: use claude for Claude Code and windsurf for Devin Desktop.

With global scope, tools share ~/.agents/skills/ or read from their own global skills folder. Eve and PromptScript need project scope.

For a tool outside the installer’s list, use --tools agents or the tool’s existing OpenSpec ID. Veai reads the universal folder in either scope. GigaCode documents the project folder. For EasyCode, keep working per-skill links or link the skills into its own folder.

Support matrix

Invocations are shown for the apply workflow. Every workflow follows the same shape. The id goes to openspec init --tools <id> to skip the picker (CLI).

Tool--tools idSkillsSkill invocation
Ampamp.agents/skills//openspec-apply-change
Antigravityantigravity.agents/skills//openspec-apply-change
AtomCodeatomcode.agents/skills//openspec-apply-change
Auggie (Augment CLI)auggie.agents/skills/ (also in .augment/skills/)/openspec-apply-change
IBM Bobbob.agents/skills/ (also in .bob/skills/)/openspec-apply-change
Claude Codeclaude.agents/skills/ (also in .claude/skills/)/openspec-apply-change
Clinecline.agents/skills//openspec-apply-change
CodeArtscodeartsagent.agents/skills/ (also in .codeartsdoer/skills/)/openspec-apply-change
CodeBuddy Code (CLI)codebuddy.agents/skills/ (also in .codebuddy/skills/)/openspec-apply-change
Code Studiocodestudio.agents/skills/ (also in .codestudio/skills/)/openspec-apply-change
Codexcodex.agents/skills/$openspec-apply-change
Continuecontinue.agents/skills/ (also in .continue/skills/)/openspec-apply-change
CoStrictcostrict.agents/skills//openspec-apply-change
Crushcrush.agents/skills/ (also in .crush/skills/)/openspec-apply-change
Cursorcursor.agents/skills//openspec-apply-change
DeepSeek Harnessdsh.agents/skills//openspec-apply-change
Devin Desktop (formerly Windsurf)devin.agents/skills/ (also in .devin/skills/)/openspec-apply-change
EasyCodeeasycode.agents/skills//openspec-apply-change
Factory Droidfactory.agents/skills//openspec-apply-change
ForgeCodeforgecode.agents/skills/ (also in .forge/skills/)/openspec-apply-change
Gemini CLIgemini.agents/skills//openspec-apply-change
GigaCodegigacode.agents/skills//openspec-apply-change
GitHub Copilotgithub-copilot.agents/skills//openspec-apply-change
Grok Buildgrok.agents/skills/ (also in .grok/skills/)/openspec-apply-change
GSDgsd.agents/skills/ask for openspec-apply-change
Hermes Agenthermes.agents/skills/ (also in .hermes/skills/)/openspec-apply-change
iFlowiflow.agents/skills/ (also in .iflow/skills/)/openspec-apply-change
Juniejunie.agents/skills/ (also in .junie/skills/)/openspec-apply-change
Kilo Codekilocode.agents/skills//openspec-apply-change
Kimi Codekimi.agents/skills//skill:openspec-apply-change
Kirokiro.agents/skills/ (also in .kiro/skills/)/openspec-apply-change
Lingmalingma.agents/skills/ (also in .lingma/skills/)/openspec-apply-change
MiniMax Codeminimax-code.agents/skills/ (also in .minimax/skills/)/openspec-apply-change
Mistral Vibevibe.agents/skills/ (also in .vibe/skills/)/openspec-apply-change
Oh My Pioh-my-pi.agents/skills//openspec-apply-change
OpenCodeopencode.agents/skills//openspec-apply-change
Pipi.agents/skills//openspec-apply-change
Qoderqoder.agents/skills/ (also in .qoder/skills/)/openspec-apply-change
Qwen Codeqwen.agents/skills/ (also in .qwen/skills/)/openspec-apply-change
Rovo Dev CLIrovodev.agents/skills/ (also in .rovodev/skills/)ask for openspec-apply-change
Traetrae.agents/skills/ (also in .trae/skills/)/openspec-apply-change
Veaiveai.agents/skills//openspec-apply-change
Warpwarp.agents/skills//openspec-apply-change
ZCodezcode.agents/skills/ (also in .zcode/skills/)/openspec-apply-change
Zoo Coderoocode.agents/skills/ (also in .roo/skills/)/openspec-apply-change
Other / Universalagents.agents/skills//openspec-apply-change
  • Skill invocation: whether a tool registers skills as typed entries is the tool's own behavior. The column shows the spelling OpenSpec uses in generated files and in the hint init prints. Check your tool's docs if typing it does nothing.

A tool that reads .agents/skills/ needs nothing: pick agents at init (Other / Universal). A tool that reads only its own folder can be pointed at the shared copy with one link. In your terminal, from the project root:

mkdir -p .mytool
ln -s ../.agents/skills .mytool/skills

On Windows, in Command Prompt:

mkdir .mytool
mklink /J .mytool\skills .agents\skills

With global skills, make the link in your home folder instead: ln -s ~/.agents/skills ~/.mytool/skills.

Replace .mytool with your tool's folder. If the tool already has a skills/ folder of its own, link each skill instead: ln -s ../../.agents/skills/openspec-propose .mytool/skills/openspec-propose.

Committing links: Git stores links as links. A teammate on Windows should run git config --global core.symlinks true (or clone with git clone -c core.symlinks=true <url>) and enable Developer Mode so links can be created. Otherwise each link checks out as a small text file, which openspec update replaces with a plain copy of the skill. A junction made with mklink /J is not committed as a link; recreate it on each machine.

Per-tool notes

A tool not listed here behaves exactly as its row reads.

Amazon Q Developer (retired)

OpenSpec 2.0 no longer supports Amazon Q Developer: it can't load skills, and AWS is retiring it in favor of Kiro. openspec init --tools amazon-q stops with that message. In a project set up for it, openspec update removes the prompts and skills OpenSpec wrote in .amazonq/, and keeps and lists any you edited. Set up Kiro instead: openspec init --tools kiro.

Antigravity

  • Current folder: Antigravity v1.20.5 and later read workspace skills and workflows from .agents/.
  • Legacy folder: after OpenSpec writes replacements, it removes equivalent generated files from .agent/. Custom files and changed generated files stay in .agent/ for you to review.
  • Shared skills: Antigravity reads the same .agents/skills/ copy as every other tool. Workflows OpenSpec wrote to .agents/workflows/ before 2.0 are removed on update.
  • Global skills: for a machine-wide install, the skills package keeps Antigravity's skills in ~/.gemini/config/skills/, as links to the shared copy or as copies. openspec update keeps them current.

Cline

Skills are the shared copy in .agents/skills/. Workflows OpenSpec wrote to .clinerules/workflows/ before 2.0 are removed on update; your own rules there are left alone.

Codex

  • CLI and IDE extension: mention $openspec-propose with your idea, or run /skills to select the skill. Codex does not recognize /openspec-propose (upstream issue).
  • Desktop app: open Skills in the sidebar and select openspec-propose. OpenAI's skills documentation describes both interfaces.
  • Shared folder: Codex reads the same .agents/skills/ copy as every other tool. Skills name each other by skill name (openspec-apply-change), which Codex invokes as $openspec-apply-change.
  • Legacy path: skills installed under .codex/skills/ by older versions are migrated on the next openspec update.

DeepSeek Harness

  • Project root: DSH uses the nearest .git ancestor, or the current directory outside Git. Run openspec init --tools dsh there. For a nested OpenSpec project, add the absolute path to its .agents/skills/ directory to DSH's customSkillDirs. Git-root skills still win if names overlap (upstream discovery rules).
  • Old copies: a .dsh/skills/ copy from before 2.0 would take precedence over .agents/skills/. openspec update removes untouched ones and reports any you changed.

Devin Desktop (formerly Windsurf)

  • Both agents: Devin Desktop and Devin Local both run the shared skills. Workflows OpenSpec wrote to .devin/workflows/ before 2.0 are removed on update.
  • Rename: --tools windsurf still resolves to devin. A project holding OpenSpec files in the legacy .windsurf/ folder is offered the move on the next openspec update.

GitHub Copilot

  • Skills: Copilot loads .agents/skills/openspec-*/SKILL.md. Invoke a skill as /openspec-<skill>. In the CLI, if a skill disappears while its file still exists, run /skills reload, then /skills info openspec-propose to confirm discovery. In an IDE, restart it.
  • Old prompt files: the .github/prompts/opsx-*.prompt.md files OpenSpec wrote before 2.0 are removed on update.

GSD

  • Project skills: GSD reads OpenSpec workflows from .agents/skills/.
  • Invocation: ask GSD to use the openspec-<workflow> skill. GSD can also select a matching skill through its skill discovery setting.
  • No subagent files: .gsd/agents/ contains GSD subagent definitions. OpenSpec does not write workflow skills there.

Hermes Agent

OpenSpec links each skill into the project's .hermes/skills/ folder. Hermes v2026.6.5 and later load that folder once you trust the repo: run hermes skills trust inside the project. Until then, Hermes shows a notice that it found project skills but did not load them. On older versions, add the project's .hermes/skills/ folder to skills.external_dirs in ~/.hermes/config.yaml instead. Init prints this reminder after install.

MiniMax Code

Project installs use .minimax/skills/. Global installs use ~/.minimax/skills/.

Warp

  • What OpenSpec claims: nothing in .warp/. Warp settings and WARP.md are not created or edited.

Other / Universal (shared .agents skills)

  • When it fits: any tool that reads the shared .agents/skills/ folder, including tools with no row in the matrix. It is the entry to pick when your assistant is not listed. The init picker's search box finds it by universal, other, generic, custom, proprietary, unlisted, unsupported, vendor-neutral, or agents.md.
  • Alongside other tools: every tool reads this one skill tree. .openspec-target lists the tools set up in the project. To remove a tool, delete its folder (or, for a tool with no folder of its own, its line in .openspec-target).
  • Custom skills: choose a name distinct from OpenSpec's built-in skills. Update replaces built-ins with the instructions from the running CLI’s GitHub release tag and leaves separately named skills alone.
  • AGENTS.md: not created or edited. The target is the .agents/ folder, not the file.

On this page