skills.rest
intent-driven-dev
intent-driven-devOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes to dated paths while preserving configuration files.

84|18|Updated Feb 11, 2026
Search Tags:#automation#workflow#archive#openspec#change-management#artifact-status#delta-specs
One-click install
npx skills add https://github.com/intent-driven-dev/openspec-schemas --skill openspec-archive-change-intent-driven-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/intent-driven-dev/openspec-schemas --skill openspec-archive-change-intent-driven-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow to preserve history and enable future audits.

Core Features & Use Cases

  • Validates change selection, checks artifact and task completion, and prompts for user confirmation before archiving.
  • Compares delta specs with main specs when available, optionally syncing before archiving, and moves the change directory to a dated archive path while preserving configuration.
  • Safely preserves project configuration files during archive and records a clear summary to aid audits.

Quick Start

Provide the change name to archive, review any warnings about incomplete artifacts or tasks, and confirm to finalize the archival.

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 OpenSpec change to preserve project history?▼

To archive a completed OpenSpec change, you provide the change name, review validation warnings for incomplete artifacts or tasks, and confirm the action to finalize the archival process.

What happens to delta specs when archiving an OpenSpec change?▼

When archiving an OpenSpec change, the process compares delta specs with main specs, assesses optional delta-spec synchronization, and moves the change directory to a dated archive path.

Can I archive an OpenSpec change if artifact or task statuses are incomplete?▼

You can attempt to archive an OpenSpec change with incomplete statuses, but the workflow enforces artifact and task status checks, warns you about incomplete items, and prompts for confirmation before proceeding.

Does the OpenSpec archival process preserve project configuration files?▼

Yes, the OpenSpec archival process safely preserves project configuration files by moving the change directory to a dated archive path while explicitly excluding and maintaining essential configuration files.

Why do I need to sync delta specs before archiving a change in OpenSpec?▼

Syncing delta specs before archiving an OpenSpec change ensures that main specifications are updated with experimental modifications, preventing the loss of finalized changes when the change directory is moved to the archive.

Related Skills

Explore More Product & Management Skills→
rock-hurock-hu

openspec-archive-change

Archive completed openspec changes into dated paths after validating artifacts and tasks.

Community
Advanced
yakksiekyakksiek

10x-archive

Move completed change folders to an archive directory and update related documents.

Community
Advanced
Pony-UnicornPony-Unicorn
7

openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

Community
Advanced
mazhewittmazhewitt

openspec-archive-change

Archives completed changes from the experimental workflow after implementation.

Community
Advanced