skills.rest
aniwei
aniweiCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed openspec changes into date-based folders via the openspec CLI.

Updated Feb 3, 2026
Search Tags:#workflow#CLI#archive#openspec#change-management#artifact-status#delta-specs
One-click install
npx skills add https://github.com/aniwei/vitamin-code --skill openspec-archive-change-aniwei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/aniwei/vitamin-code/tree/main/refs/opencode/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/aniwei/vitamin-code --skill openspec-archive-change-aniwei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow to finalize and preserve prior work. Without a formal archive, changes can be difficult to audit, recover, or compare against main lines.

Core Features & Use Cases

  • Archive status and change metadata are preserved with a date-stamped archive path.
  • Prompts guide users to confirm artifact and task completion, and optionally sync delta specs before archiving.
  • Archive movement preserves the .openspec.yaml file and places the change under openspec/changes/archive/YYYY-MM-DD-<name> for traceability.

Quick Start

Select the change you want to archive when prompted. The system will verify artifacts and tasks, assess delta-spec synchronization if present, and move the archived change into openspec/changes/archive with a date-based folder name.

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 completed changes in openspec?▼

To archive completed changes, select the target change when prompted, and the system verifies artifact status, evaluates delta specs, then moves it into openspec/changes/archive with a date-stamped folder name.

When should I archive a change in the openspec workflow?▼

You should archive a change in the openspec workflow after development, verification, and validation are complete, ensuring prior work is finalized and preserved for auditability and recovery.

Do I need the openspec CLI to archive changes?▼

Yes, you need the openspec CLI to archive changes, as the workflow requires it to check artifact status via openspec status --json and evaluate delta specs before moving the change.

What happens to delta specs when archiving a change?▼

When archiving a change, the system evaluates delta specs and optionally syncs them before moving the change into the archive directory, ensuring traceability and preserving the .openspec.yaml file.

Can I recover or audit changes after moving them to the archive?▼

Yes, archived changes are preserved with a date-stamped path under openspec/changes/archive/YYYY-MM-DD-<name>, making them easy to audit, recover, or compare against main lines.

Why does archiving changes fail if artifacts are incomplete?▼

Archiving changes requires artifact and task completion confirmation; incomplete artifacts prevent finalization because the system checks status via openspec status --json before proceeding.

Related Skills

Explore More Software Engineering Skills→
bacocobacoco
67

openspec-change-closure

Archive completed OpenSpec changes by merging delta specs into living specifications.

Community
Advanced
seanmarsseanmars

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
JanuaryLabsJanuaryLabs
4

openspec-archive-change

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

Official
Advanced
jonathanhu237jonathanhu237

openspec-archive-change

Archive completed openspec changes into a date-stamped directory.

Community
Intermediate