skills.rest
agentxm
agentxmOFFICIAL
Explore all skills by this author →
Website𝕏@agentxm_aiGitHub

openspec-archive-change

Archive completed OpenSpec changes to dated directories with delta-spec synchronization.

5|Updated Jan 29, 2026
Search Tags:#workflow#archive#openspec#change-management#artifact-status#delta-specs
One-click install
npx skills add https://github.com/agentxm/axm --skill openspec-archive-change-agentxm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/agentxm/axm/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/agentxm/axm --skill openspec-archive-change-agentxm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow to finalize and organize artifacts after implementation.

Core Features & Use Cases

  • Interactive change selection and prompts for archival decisions to avoid data loss.
  • Artifact status verification, delta-spec synchronization, and safe archiving to openspec/changes/archive.
  • Preservation of configuration files (like .openspec.yaml) during archival and a final summary report.

Quick Start

Provide the change name when prompted and follow the on-screen prompts to archive the change.

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 OpenSpec changes after implementation?▼

Archive completed OpenSpec changes by providing the change name, allowing the tool to check artifact completion, synchronize delta-specs, and move files to openspec/changes/archive. Configuration files like .openspec.yaml are preserved during the process.

What is delta-spec synchronization in change-management workflows?▼

Delta-spec synchronization in change-management workflows verifies artifact statuses and coordinates updates before archiving. This ensures experimental workflow changes are safely finalized and organized after implementation.

Does the OpenSpec archiving process preserve .openspec.yaml configuration files?▼

Yes, the OpenSpec archiving process preserves .openspec.yaml configuration files. When moving completed changes to openspec/changes/archive, the tool maintains the original configuration structure to prevent data loss.

How do I safely move implemented changes to an archive directory?▼

Safely move implemented changes to an archive directory by using interactive prompts and artifact status verification. The tool coordinates delta-spec synchronization and archives files to openspec/changes/archive/YYYY-MM-DD-<name> with a final summary report.

What are the limitations of archiving OpenSpec changes without artifact verification?▼

Archiving OpenSpec changes without artifact verification risks data loss and incomplete delta-spec synchronization. Interactive prompts for archival decisions ensure all artifacts are completed and properly coordinated before moving to the archive directory.

When do I need to archive a completed change in the experimental workflow?▼

You need to archive a completed change in the experimental workflow after implementation is finished. This finalizes the change-management process by organizing artifacts and moving them to the archive with a dated folder structure for tracking.

Related Skills

Explore More Software Engineering Skills→
woutervanranstwoutervanranst
1

openspec-archive-change

Archives completed OpenSpec changes with delta sync and artifact validation.

Community
Advanced
kevinxo328kevinxo328
5

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes while resolving delta-spec conflicts.

Community
Advanced
rock-hurock-hu

openspec-new-change

Scaffold a new OpenSpec change with the artifact-driven workflow.

Community
Advanced
accidental-hedge-fundaccidental-hedge-fund
3

openspec-archive-change

Archive completed openspec experimental changes to dated directories with validation.

Official
Intermediate