name	openspec-bulk-archive-change
description	Use when working with OpenSpec in Hermes: archive multiple completed changes and handle spec conflicts.
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-bulk-archive-change

Use this for OpenSpec's /opsx:bulk-archive 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

List active changes: openspec list --json.
Select target changes. If not named, find completed changes by reading status and task checkboxes.
Validate each target change.
Detect conflicts where multiple changes touch the same spec files.
Resolve conflicts by checking implementation evidence and chronological creation order. Do not blindly overwrite spec content.
Archive one at a time with openspec archive <name> --yes.
Run openspec validate --all after the batch.
Report archived changes, merge order, conflicts handled, and skipped changes.

Más de este repositorio

mismo repositorio

openspec-apply-change

TheSmuks/openspec-hermes

Use when working with OpenSpec in Hermes: implement tasks from an OpenSpec change and keep task checkboxes updated.

2026-06-220

openspec-archive-change

TheSmuks/openspec-hermes

Use when working with OpenSpec in Hermes: archive one completed change, optionally syncing specs first.

2026-06-220

openspec-cli

TheSmuks/openspec-hermes

Use when working with OpenSpec in Hermes: manage OpenSpec CLI setup, validation, browsing, workspaces, context stores, initiatives, and shell integration.

2026-06-220

openspec-continue-change

TheSmuks/openspec-hermes

Use when working with OpenSpec in Hermes: create the next ready artifact based on the schema dependency graph.

2026-06-220

openspec-customize

TheSmuks/openspec-hermes

Use when working with OpenSpec in Hermes: customize OpenSpec project config, rules, templates, and schemas.

2026-06-220

openspec-expanded-path

TheSmuks/openspec-hermes

Use when working with OpenSpec in Hermes: run the expanded OpenSpec scaffold, fast-forward, apply, verify, and optional archive workflow end to end.

2026-06-220

openspec-bulk-archive-change

Use this for OpenSpec's /opsx:bulk-archive 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

List active changes: openspec list --json.

Select target changes. If not named, find completed changes by reading status and task checkboxes.

Validate each target change.

Detect conflicts where multiple changes touch the same spec files.

Resolve conflicts by checking implementation evidence and chronological creation order. Do not blindly overwrite spec content.

Archive one at a time with openspec archive <name> --yes.

Run openspec validate --all after the batch.

Report archived changes, merge order, conflicts handled, and skipped changes.