Skip to content
AIBRAINWORX / OpenSourceCoder.comLOCAL-FIRST. BUILT IN THE OPEN.
Developer & Agent Tools / Text & Coding LLMs / Enterprise & Legal

OpenSpec 2.0 consolidates skills and removes old slash commands

The spec-driven coding tool moves to a shared skills folder; its maintainers warn that some edited skill files can be overwritten on update.

Listen to this articleBrowser Voice
Ready
Official OpenSpec project banner
Fission AI / OpenSpec, official repository banner.
Event / context: OpenSpec v2.0.0 was released November 11, 2026.. Source check: October 28, 2026.

OpenSpec 2.0 moves its coding-agent workflow skills into a shared .agents/skills/ directory and removes the older /opsx:* slash commands. The MIT-licensed project’s November 11 release notes say the underlying workflows remain the same, with each former command represented by a corresponding skill.

The change affects project setup for developers who use OpenSpec to organize proposals, specifications and implementation tasks with coding assistants. Tools that do not read the shared directory receive links to the same skills, according to the maintainers.

Review before updating

The release notes recommend previewing migration with openspec update --dry-run. They say the update removes certain generated files from older installations, while edited files in old locations are kept and listed. There is an important exception: edits made directly inside skills installed in the shared .agents/skills/ directory are overwritten. Save those edits before applying an update.

OpenSpec 2.0 also removes support for Amazon Q Developer because, the maintainers say, it cannot load the new skills. Existing delivery configuration can remain, but is no longer required. Teams should check their own agent integrations and project changes before committing an upgrade.

Where to inspect the code

The OpenSourceCoder.com repository profile links to the upstream source, release notes and upgrade documentation. A shared folder can reduce duplicate configuration, but a single copy also makes careful review of generated updates more important when several tools depend on it.

We have not installed or tested OpenSpec 2.0; the migration behavior above is reported by its maintainers.

EXPLORE THE SOURCE

GitHub repositories

Original reporting; primary sources reviewed November 14, 2026. No independent hands-on test claimed.

Follow your curiosity.

Pass the signal.