Supported Tools

OpenSpec works with many AI coding assistants. When you run openspec init, OpenSpec configures selected tools using your active profile/workflow selection and delivery mode.

How It Works

For each selected tool, OpenSpec can install:

1. Skills (if delivery includes skills): .../skills/openspec-*/SKILL.md
2. Commands (if delivery includes commands): tool-specific opsx-* command files

Codex is skills-only: OpenSpec installs .codex/skills/openspec-*/SKILL.md for Codex even when delivery is set to commands, and it does not generate Codex custom prompt files.

By default, OpenSpec uses the core profile, which includes:

• propose
• explore
• apply
• update
• sync
• archive

You can enable expanded workflows (new, continue, ff, verify, bulk-archive, onboard) via openspec config profile, then run openspec update.

How To Invoke

These docs use /opsx:propose as the canonical name, but each tool spells it the way it loads the file OpenSpec wrote. Find your tool's command path in the Tool Directory Reference below, then match its shape here.

So /opsx:propose is /opsx-propose in Cursor, @opsx-propose in Amazon Q, and $openspec-propose in Codex.

Two things vary independently, which is why the rows do not collapse:

• The name. Rows 1–2 differ only in how the file names the command, and the opsx-<id> / opsx:<id> stem is the same for every tool with generated command files.
• The wrapper. Amazon Q loads its files into a prompt library invoked with @. Skills-only tools generate no command files at all, so their last three rows use skill names — listed under Generated Skill Names — which do not map one-to-one onto command ids (/opsx:apply is the openspec-apply-change skill).

The command path patterns above are extension-neutral (.*) on purpose: the extension is the tool's (.toml for Gemini CLI, .prompt for Continue, .prompt.md for Kiro and GitHub Copilot), and a few tools show the name with its extension in the picker. Match the directory shape, not the extension.

The files OpenSpec generates, and the "Getting started" hint printed after setup, already use the right form for the tools you selected — so the fastest answer is to read the hint.

Tool Directory Reference

** GitHub Copilot prompt files are recognized as custom slash commands in IDE extensions (VS Code, JetBrains, Visual Studio). Copilot CLI does not currently consume .github/prompts/*.prompt.md directly.

*** Hermes loads skills from ~/.hermes/skills/ by default. To use project-local OpenSpec skills, add the project .hermes/skills/ directory to skills.external_dirs in ~/.hermes/config.yaml; Hermes then exposes skills with user-facing slash invocations such as /openspec-propose.

**** Windsurf was rebranded to Devin Desktop on June 2, 2026, and its config directory moved: .devin/ is the preferred read + write location, .windsurf/ a legacy read-only fallback. OpenSpec follows the rename — the tool id is devin, and --tools windsurf still resolves to it so existing setup scripts keep working. A project still holding OpenSpec files in .windsurf/ is offered the move on the next openspec update; declining leaves them in place, and files you wrote yourself are never touched. Workflows are invoked by filename, so .devin/workflows/opsx-apply.md is /opsx-apply. The Devin Local agent does not support workflows — only skills, and it does not read .windsurf/ at all — so whenever OpenSpec writes Devin skills it keeps their bodies, and the getting-started hint, on /openspec-* skill invocations, which work on both agents. Under commands-only delivery no skills are written and both fall back to /opsx-*.

Non-Interactive Setup

For CI/CD or scripted setup, use --tools (and optionally --profile):

# Configure specific tools
openspec init --tools claude,cursor

# Configure all supported tools
openspec init --tools all

# Skip tool configuration
openspec init --tools none

# Override profile for this init run
openspec init --profile core

Available tool IDs (--tools) — windsurf is also accepted, as an alias for devin: amazon-q, antigravity, auggie, bob, claude, cline, codeartsagent, codex, devin, forgecode, codebuddy, continue, costrict, crush, cursor, factory, gemini, github-copilot, hermes, iflow, junie, kilocode, kimi, kiro, lingma, vibe, oh-my-pi, opencode, pi, qoder, qwen, roocode, trae, zcode

Workflow-Dependent Installation

OpenSpec installs workflow artifacts based on selected workflows:

• Core profile (default): propose, explore, apply, update, sync, archive
• Custom selection: any subset of all workflow IDs: propose, explore, new, continue, apply, update, ff, sync, archive, bulk-archive, verify, onboard

In other words, skill/command counts are profile-dependent and delivery-dependent, not fixed.

Generated Skill Names

When selected by profile/workflow config, OpenSpec generates these skills:

• openspec-propose
• openspec-explore
• openspec-new-change
• openspec-continue-change
• openspec-apply-change
• openspec-update-change
• openspec-ff-change
• openspec-sync-specs
• openspec-archive-change
• openspec-bulk-archive-change
• openspec-verify-change
• openspec-onboard

See Commands for command behavior and CLI for init/update options.

Related

• CLI Reference — Terminal commands
• Commands — Slash commands and skills
• Getting Started — First-time setup