| name | openspec-cli |
| description | Use when working with OpenSpec in Hermes: manage OpenSpec CLI setup, validation, browsing, workspaces, context stores, initiatives, and shell integration. |
| version | 1.0.0 |
| author | TheSmuks + Hermes Agent |
| license | MIT |
| platforms | ["windows","macos","linux"] |
| metadata | {"hermes":{"category":"software-development","tags":["openspec","sdd","spec-driven-development","hermes"],"homepage":"https://github.com/Fission-AI/openspec"}} |
openspec-cli
Use for OpenSpec CLI administration and non-workflow features.
Hermes operating rules for OpenSpec
- Work from the user's project root. If unknown, inspect the current directory first.
- Ensure the OpenSpec CLI exists before using it:
openspec --version. If missing, install with npm install -g @fission-ai/openspec@latest.
- Initialize projects with
openspec init --tools none unless the user also wants other AI-tool integrations. Hermes uses these skills, not OpenSpec-generated slash commands.
- Prefer agent-compatible OpenSpec CLI calls with
--json where available: openspec list --json, openspec status --change <id> --json, openspec instructions <artifact> --change <id> --json, openspec validate --all --json.
- Read generated artifacts before editing or implementing. Do not invent OpenSpec state.
- Run validation after changing OpenSpec artifacts:
openspec validate <change> or openspec validate --all.
- Keep changes focused. If user scope diverges, update the existing change only when intent is the same; otherwise create a new change.
Setup and update
- Install/upgrade:
npm install -g @fission-ai/openspec@latest
- Init project for Hermes:
openspec init --tools none
- Refresh OpenSpec-generated files if the user uses other tools too:
openspec update
Agent-compatible inspection
openspec list --json
openspec list --specs --json
openspec show <item> --json
openspec validate --all --json
openspec status --change <id> --json
openspec instructions <artifact> --change <id> --json
openspec templates --json
openspec schemas --json
Workspaces and shared context
openspec workspace setup --no-interactive --name <name> --link <path> --json
openspec workspace list --json
openspec workspace link <name> <path> --json
openspec workspace doctor --json
openspec workspace update --tools none
openspec workspace open --editor or --agent <tool>
openspec context-store setup <id> --json --no-init-git
openspec context-store register <path> --json
openspec context-store list --json
openspec context-store doctor <id> --json
openspec initiative create <id> --title <title> --summary <summary> --json
openspec initiative list --json
openspec initiative show <id> --json
Completion and feedback
- Shell completions:
openspec completion install bash|zsh|fish|powershell
- Feedback:
openspec feedback "message" --body "details" requires gh auth.