Archive multiple completed changes in a single operation.

This skill allows you to batch-archive changes, handling spec conflicts intelligently by checking the codebase to determine what's actually implemented.

Store selection:

If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run

openspec store list --json

to discover registered store ids, then pass

--store

on the commands that read or write specs and changes (

new change

,

status

,

instructions

,

list

,

show

,

validate

,

archive

,

doctor

,

context

,

schemas

,

view

). Once selected, treat

--store

as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run

openspec status --change "" --json --store ""

, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local

openspec/

root.

is the spec directory relative to

specs/

(for example,

user-auth

or

identity/user-auth

). Preserve the full path from each delta spec when resolving its main spec.

Input

None required (prompts for selection) Steps Get active changes Run openspec list --json to get all active changes. If no active changes exist, inform user and stop. Prompt for change selection Show more Installs 989 Repository fission-ai/openspec GitHub Stars 66.9K First Seen Jul 17, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Warn