openspec-archive-change

Archive completed openspec changes after verifying artifacts and syncing delta specs.

4|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-archive-change-januarylabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/JanuaryLabs/deepagents/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-archive-change-januarylabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the finalization and archival of experimental changes managed by the openspec workflow, ensuring teams do not leave incomplete artifacts or unsynced delta specs when closing a change.

Core Features & Use Cases

  • Guided Selection: Prompts the user to select an active change when no name is provided, preventing accidental archival of the wrong item.
  • Completion Verification: Checks artifact completion via openspec status and scans task lists for unfinished tasks, asking for confirmation before proceeding.
  • Delta Spec Assessment & Syncing: Detects delta specs, compares them to main specs, summarizes the diffs, and offers to sync changes before archiving.
  • Safe Archival: Creates a dated archive folder, preserves metadata like .openspec.yaml, prevents overwriting existing archives, and reports a clear summary of actions and warnings.
  • Use Case: A developer finalizing a feature change can validate artifacts and tasks, optionally sync specification updates, and reliably move the change to openspec/changes/archive with auditability.

Quick Start

Archive the change named add-user-auth by prompting to select it, validating artifacts and tasks, optionally syncing delta specs, and moving the folder into openspec/changes/archive.

Frequently Asked Questions about openspec-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive a completed change in openspec and verify unfinished tasks?

Archiving completed changes in openspec involves verifying artifact completion and resolving delta spec differences before moving the directory. It ensures teams do not leave incomplete artifacts or unsynced specifications when closing a change.

How do I sync delta specs to main specs before archiving an openspec change?

Syncing delta specs before archiving an openspec change requires detecting the delta specs, comparing them to main specs, and summarizing the differences. The workflow then offers to sync the changes before moving the folder to the archive.

Can I select which openspec change to archive if I have multiple active changes?

Yes, when no specific change name is provided, the openspec CLI lists active changes and prompts the user to select one. This guided selection prevents accidental archival of the wrong item in the openspec/changes directory.

Does the openspec archive process preserve metadata like the .openspec.yaml file?

Yes, the openspec archive process preserves metadata such as the .openspec.yaml file. It creates a dated archive folder within openspec/changes/archive, prevents overwriting existing archives, and maintains full auditability.

What happens if I try to archive an openspec change with incomplete artifacts?

If you attempt to archive an openspec change with incomplete artifacts, the workflow checks completion via openspec status and scans for unfinished tasks. It will ask for your confirmation before proceeding with the archival.