Question on OpenSpec Command Support in IDE Tools: Why are Extended Commands (e.g., /opsx:ff) Less Prevalent Than Core Commands?

[HowardYan888]

Hello everyone,

I have a question regarding OpenSpec command support that I'd like to discuss. I've noticed that in IDE integration tools like CodeBuddy, we typically only have access to basic OpenSpec core commands (e.g., /opsx:propose, /opsx:apply, /opsx:archive). However, extended workflow commands, such as /opsx:ff, don't seem to be consistently supported or recognized by default. According to OpenSpec documentation, /opsx:ff is part of the expanded workflow commands, designed to "create all planning artifacts at once" (Fast-forward: create all planning artifacts at once), which is similar to /opsx:propose but potentially covers a broader scope of artifact generation.

I'm curious about the reasons behind this. Is it due to:

[clay-good]

Good question, and the answer is simpler than it looks: it is not the tool, it is the profile.

OpenSpec installs a profile, and the default core profile only includes propose, explore, apply, sync, and archive. ff lives in the expanded set (new, continue, ff, verify, bulk-archive, onboard), which is opt-in. So a freshly initialized project shows only the core five regardless of which tool you picked.

CodeBuddy is not the limitation here. It has a full command adapter (.codebuddy/commands/opsx/<id>.md, see docs/supported-tools.md), so /opsx:ff works there once the profile includes it:

openspec config profile   # add new, continue, ff, verify, etc.
openspec update           # regenerate the command/skill files for your tools

The profile split is documented in docs/supported-tools.md and under Profile in docs/glossary.md. Closing as answered.