skills.rest
guillaumejay
guillaumejayCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed experimental workflow changes with metadata preservation.

Updated Jan 30, 2026
Search Tags:#automation#workflow#artifacts#archive#openspec#change-management#spec-sync
One-click install
npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-archive-change-guillaumejay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/guillaumejay/FileIndexer/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-archive-change-guillaumejay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives a completed change from the experimental workflow to keep history, context, and auditing intact while keeping the active workspace clean.

Core Features & Use Cases

  • Prompts for change selection if none is provided, ensuring deliberate archiving decisions.
  • Verifies artifact and task completion status before archiving.
  • Archives the change by moving its directory into openspec/changes/archive with a date-based name, preserving metadata.
  • Optionally synchronizes delta specs with main specs when available.

Quick Start

Archive a completed change by selecting or providing a change name, then confirm archiving and any necessary spec syncing.

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 an experimental workflow?▼

To archive completed changes, you select or provide a change name, then the workflow moves its directory into openspec/changes/archive with a date-based name. This preserves metadata and keeps the active workspace clean.

What happens to delta specs when I archive a change?▼

Delta specs are optionally synchronized with main specs during the archiving process when available. This ensures the main specifications reflect the completed changes while preserving the archived history.

How does the archiving process verify changes are ready to be archived?▼

The archiving process verifies artifact and task completion status before moving the change directory. It also prompts for change selection if none is provided, ensuring deliberate archiving decisions through enforced guardrails.

Can I archive changes without specifying which one to archive?▼

Yes, the workflow prompts you to select a change if none is provided. This guardrail ensures deliberate archiving decisions and prevents accidentally archiving the wrong experimental change.

Why should I archive completed changes instead of leaving them active?▼

Archiving completed changes keeps your history, context, and auditing intact while keeping the active workspace clean. It moves the change directory to a date-based archive folder, preserving all metadata for future reference.

Related Skills

Explore More Software Engineering Skills→
KahtafKahtaf
9

source-command-opsx-archive

Archive completed changes in an experimental workflow with delta spec sync.

Community
Intermediate
rangechowrangechow

openspec-sync-specs

Merge delta specs into main specs with idempotent updates.

Community
Advanced
kevintsengtwkevintsengtw
1

openspec-archive-change

Archive completed changes with status checks and optional delta spec sync.

Community
Advanced
MeetTechnologyMeetTechnology

openspec-archive-change

Archive completed openspec changes with artifact and task completion checks.

Community
Advanced