Openspec Bulk Archive Change

Detect spec conflicts

Build a map of capability -> [changes that touch it]:

auth -> [change-a, change-b]  <- CONFLICT (2+ changes)
api  -> [change-c]            <- OK (only 1 change)

A conflict exists when 2+ selected changes have delta specs for the same capability.

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:

• Which change's specs to apply
• In what order (if both)
• Rationale (what was found in codebase)

Show consolidated status table

Display a table summarizing all changes:

| Change               | Artifacts | Tasks | Specs   | Conflicts | Status |
|---------------------|-----------|-------|---------|-----------|--------|
| schema-management   | Done      | 5/5   | 2 delta | None      | Ready  |
| project-config      | Done      | 3/3   | 1 delta | None      | Ready  |
| add-oauth           | Done      | 4/4   | 1 delta | auth (!)  | Ready* |
| add-verify-skill    | 1 left    | 2/5   | None    | None      | Warn   |

For conflicts, show the resolution:

* Conflict resolution:
  - auth spec: Will apply add-oauth then add-jwt (both implemented, chronological order)

For incomplete changes, show warnings:

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

Confirm batch operation

Use AskUserQuestion tool with a single confirmation:

• "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.

Execute archive for each confirmed change

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

a. Sync specs if delta specs exist:

• Use the openspec-sync-specs approach (agent-driven intelligent merge)
• For conflicts, apply in resolved order
• Track if sync was done

b. Perform the archive:

mkdir -p openspec/changes/archive
mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>

c. Track outcome for each change:

• Success: archived successfully
• Failed: error during archive (record error)
• Skipped: user chose not to archive (if applicable)

Display summary

Show final results:

## Bulk Archive Complete

Archived 3 changes:
- schema-management-cli -> archive/2026-01-19-schema-management-cli/
- project-config -> archive/2026-01-19-project-config/
- add-oauth -> archive/2026-01-19-add-oauth/

Skipped 1 change:
- add-verify-skill (user chose not to archive incomplete)

Spec sync summary:
- 4 delta specs synced to main specs
- 1 conflict resolved (auth: applied both in chronological order)

If any failures:

Failed 1 change:
- some-change: Archive directory already exists