OpenSpec Archive Skill

Use /opsx:archive to finalize a completed change. Archives by merging delta specs into the main openspec/specs/ directory and moving the change folder to openspec/changes/archive/.

When to Use

• Implementation is complete and verified.
• The user says “archive”, “finish”, “done with this change”, “wrap up”.
• After running openspec-verify (optional but recommended).

Prerequisites

• Change exists with artifacts and (ideally) completed tasks.

Workflow

1. Run archive

   • /opsx:archive — archive the current/inferred change.
   • /opsx:archive <change-name> — archive a specific change.

2. What happens

   1. Checks artifact completion status and task completion (warns if incomplete).
   2. Offers to sync delta specs if not already synced (see openspec-sync).
   3. Merges delta specs into openspec/specs/ (ADDED / MODIFIED / REMOVED sections).
   4. Moves the change folder to openspec/changes/archive/YYYY-MM-DD-<name>/.

3. All artifacts preserved

   • The full change context (proposal, design, tasks, specs) is preserved in the archive for audit trail.

Delta Spec Merge Rules

Outputs

• Delta specs merged into openspec/specs/.
• Change moved to openspec/changes/archive/YYYY-MM-DD-<name>/.

Next Steps

• Start a new change with openspec-new.
• The main specs now reflect the changes — future changes build on the updated source of truth.

Troubleshooting

• “Incomplete tasks”: Archive warns but does not block. Decide whether to complete tasks first or archive as-is.
• “Delta specs not synced”: Archive will prompt to sync; or run openspec-sync beforehand.
• Multiple changes to archive: Use openspec-bulk-archive instead.

References

• OpenSpec Commands: /opsx:archive
• OpenSpec Concepts: Archive