openspec-new-change

name	openspec-new-change
description	Use when working with OpenSpec in Hermes: create only the change scaffold for expanded workflows.
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-new-change

Use this for OpenSpec's /opsx:new workflow.

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.

Procedure

1. Determine a kebab-case change name. Avoid generic names like update, changes, or wip.
2. Ensure OpenSpec is initialized.
3. Create the scaffold with openspec new change <name> --json. Add --schema <schema> if requested.
4. Inspect status: openspec status --change <name> --json.
5. Report the change folder, schema, and first ready artifact. Do not write proposal/spec/design/tasks unless the user asked for fast-forward or continuation.

Optional flags: --description, --goal, --areas, --initiative, --store, --store-path.