yinzhenyu-su/qrypt/openspec-bulk-archive-change

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 <id> 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 <id> 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 "<name>" --json --store "<id>", 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.

<capability-path> 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

1. Get active changes

Run openspec list --json to get all active changes.

If no active changes exist, inform user and stop.

1. Prompt for change selection

Ask the user to choose changes (multi-select):

• Show each change with its schema
• Include an option for "All changes"
• Allow any number of selections (1+ works, 2+ is the typical use case)

IMPORTANT: Do NOT auto-select. Always let the user choose.

Load current archive inputs once for the selected root before batch validation:

Choose one selected change from this root and run openspec instructions archive --change "<selected-change>" --json with the same selected-root flags. This lookup is advisory and optional: it only supplies extra prompt inputs, so it must never block the batch. If it fails or returns invalid JSON — for example on an older CLI that does not support this command yet — continue the batch with no context and no operation guidance. Do not report an error and do not stop.

A valid response may omit context and operationGuidance. Treat context as a required prompt-level input across the batch: read and consider it, and apply relevant project facts, conventions, and constraints. Treat operationGuidance as optional additive advice: read and consider every entry, and follow entries that are applicable and compatible with the built-in batch workflow.

Keep both fields separate from conflict analysis, explicit user choices, resolved paths, CLI checks, and command contracts. If context conflicts with one of those controlling inputs, report the conflict and preserve the controlling value. If guidance is inapplicable or conflicts with a controlling input, do not follow it and explain why. Do not infer skipped prompts, replacement paths, or flags from either field, and do not copy their text verbatim into specs, changes, or summaries. These are prompt-level behavior contracts, not enforceable checks.

1. Batch validation - gather status for all selected changes

For each selected change, collect:

a. Artifact status - Run openspec status --change "<name>" --json

• Parse schemaName, artifacts, planningHome, changeRoot, artifactPaths, and actionContext
• Note which artifacts are done vs other states

b. Task completion - Read artifactPaths.tasks.existingOutputPaths from status JSON

• Count - [ ] (incomplete) vs - [x] (complete)
• If no tasks file exists, note as "No tasks"

c. Delta specs - Check artifactPaths.specs.existingOutputPaths from status JSON

• List which capability specs exist
• For each, extract requirement names (lines matching ### Requirement: <name>)
• Treat this list as the only delta-spec source. If the specs entry is

missing or the list is empty, perform no spec sync or specs-instruction lookup for that change; do not infer deltas from unrelated artifacts.

• Evaluate this independently for every change, including mixed-schema

batches where some schemas have no specs artifact.

1. Detect spec conflicts

Build a map keyed by <capability-path>, the exact path relative to specs/:

``text identity/user-auth -> [change-a, change-b] <- CONFLICT (2+ changes) billing/user-auth -> [change-c] <- OK (different full path) ``

A conflict exists when 2+ selected changes have delta specs for the exact same <capability-path>.

1. Resolve conflicts agentically

For each conflict, investigate the codebase:

a. Read the delta specs from each conflicting change to understand what each claims to add/modify

b. Search the codebase for implementation evidence:

• Look for code implementing requirements from each delta spec
• Check for related files, functions, or tests

c. Determine resolution:

• If only one change is actually implemented -> sync that one's specs
• If both implemented -> apply in chronological order (older first, newer overwrites)
• If neither implemented -> skip spec sync, warn user

d. Record resolution for each conflict:

• An inclusion or exclusion decision for every delta spec, keyed by change and <capability-path>
• Which included delta specs to apply and in what order
• Which delta specs to exclude from sync because their implementation is missing
• Rationale (what was found in codebase)

1. Show consolidated status table

Display a table summarizing all changes:

```markdown

```

For conflicts, show the resolution: ```text

• Conflict resolution:
• identity/user-auth spec: Will apply add-oauth then add-jwt (both implemented, chronological order)

```

For incomplete changes, show warnings: ```text Warnings:

• add-verify-skill: 1 incomplete artifact, 3 incomplete tasks

```

1. Confirm batch operation

Ask the user a single confirmation question:

• "Archive N changes?" with options based on status
• Options might include:
• "Archive all N changes"
• "Archive only N ready changes (skip incomplete)"
• "Cancel"

If there are incomplete changes, make clear they'll be archived with warnings.

Route on the answer by intent, not by exact label — you wrote these labels, so match what the user picked rather than the wording above:

• "Cancel" — stop, do not archive. Report that nothing was archived and skip the remaining steps.
• The archive-everything option — proceed with every selected change
• The ready-only option — proceed with only the changes the step 6 table marks Ready or Ready*, and record the rest as Skipped in step 8d. If a Ready* change's conflict partner is skipped, re-derive that conflict's resolution using only the changes being archived.
• Anything else — ask again rather than archiving

Before step 8 writes the first main spec or moves any change, fetch every required specs-rule snapshot for the confirmed batch. For each change that will sync concrete artifactPaths.specs.existingOutputPaths, run openspec instructions specs --change "<name>" --json exactly once with the same selected-root flags. Obtain all snapshots before the first write or move. If any lookup exits non-zero or returns invalid artifact-instruction JSON, identify the affected change, report the error, and stop the whole batch before any main-spec write or change move. Do not treat lookup failure as omitted rules. A valid response without rules is the no-rules case.

1. Execute archive for each confirmed change

Before processing, carry the recorded decisions from step 5 (after any step 7 re-derivation) into two per-delta sets:

• includedDeltas: all non-conflicting delta specs from confirmed changes plus conflict deltas selected for sync
• excludedDeltas: conflict deltas from confirmed changes excluded because their implementation is missing
• A single change can have both included and excluded delta specs. Keep the decision per delta; do not collapse it into a per-change sync flag.

Process changes in the determined order (respecting conflict resolution):

a. Sync included delta specs:

• Run the openspec-sync-specs workflow inline (agent-driven intelligent merge) only for changes with entries in includedDeltas, passing only the included delta paths and explicitly instructing it to ignore that change's excludedDeltas. Wait for it to finish.
• For conflicts, apply in resolved order.
• Pass that change's fetched specs-rule snapshot into inline sync; inline

sync must reuse it without fetching instructions again

• Apply artifact rules only to main specs produced by that change. They do

not change conflict resolution, archive behavior, or CLI contracts, and their text is not copied into an output file

• Do not delegate to a background task — step 8c would move changeRoot out from under a sync that is still reading it.
• If a change has no included delta specs, do not run the sync workflow for it.

b. Verify included delta specs before moving changeRoot:

• Re-run the comparison only for delta specs in includedDeltas against main spec at <planningHome.root>/openspec/specs/<capability-path>/spec.md (use the store-aware planningHome.root from step 3 status JSON, not a hardcoded repo path).
• Verify that main specs are updated:
• ADDED requirements present
• MODIFIED requirements carrying scenario and description changes named in the delta, with their other scenarios intact
• REMOVED requirements gone — and where this sync retired a capability (removed its last requirement, leaving ## Requirements empty), its main spec deleted rather than left empty; a spec the sync deliberately kept and reported is also a match
• RENAMED requirements present under the new name and absent under the old one
• Do not verify delta specs in excludedDeltas; they are intentionally left unsynced.
• If sync failed or any capability does not match verification, report what differs and fail/skip moving that change's changeRoot — do not archive that change. changeRoot remains intact.

c. Perform the archive:

Target name: use the change name as-is when it already starts with a YYYY-MM-DD- prefix; otherwise prepend the current date as YYYY-MM-DD-<name> (same rule as openspec archive).

``bash mkdir -p "<planningHome.changesDir>/archive" mv "<changeRoot>" "<planningHome.changesDir>/archive/<target-name>" ``

d. Track outcome for each change:

• Success: archived successfully
• Failed: error during archive or spec verification (record error)
• Skipped: user chose not to archive (if applicable)
• Sync skipped: for every delta in excludedDeltas, report sync skipped with the change, <capability-path>, and recorded reason. This is distinct from skipping the archive.

1. Display summary

Show final results: