skills.rest
rafazafar
rafazafarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes to a date-stamped directory after validation.

Updated Apr 11, 2026
Search Tags:#automation#workflow#validation#archive#openspec#delta-spec#spec-management
One-click install
npx skills add https://github.com/rafazafar/codex-octopus --skill openspec-archive-change-rafazafar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/rafazafar/codex-octopus/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/rafazafar/codex-octopus --skill openspec-archive-change-rafazafar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow after implementation, ensuring proper validation and a clear archival trail.

Core Features & Use Cases

  • Interactive change selection to identify which change to archive.
  • Artifact and task status checks to confirm completion before archiving.
  • Delta-spec synchronization assessment with optional syncing and clear delta summary.
  • Safe archiving to openspec/changes/archive/YYYY-MM-DD-<name>, preserving important metadata.
  • Comprehensive summary reporting after the archive.

Quick Start

Run this skill after a change is implemented to archive it to the archive directory and generate a final status summary.

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

To archive completed changes safely, this skill validates artifact and task completion, assesses delta spec synchronization, and moves the change to a date-stamped directory while preserving metadata.

What is delta spec synchronization and does it need to be checked before archiving?▼

Delta spec synchronization ensures completed changes align with the main specification. This skill assesses delta spec status before archiving and offers optional syncing to prevent inconsistencies.

How do I move completed OpenSpec changes to an archive directory?▼

You can move completed OpenSpec changes by running this skill, which interactively prompts for change selection, verifies completion status, and archives the change to openspec/changes/archive/YYYY-MM-DD-<name>.

Can I archive a change if artifact and task completion checks have not passed?▼

No, artifact and task status checks must confirm completion before archiving. This validation ensures only fully implemented changes are archived, preventing incomplete work from entering the archive.

What is the best way to maintain an archival trail for completed spec management changes?▼

The best way to maintain an archival trail is to archive changes to a date-stamped directory. This skill generates a comprehensive summary report after archiving, ensuring a clear validation record.

When should I not use an automated archiving process for workflow changes?▼

You should not use automated archiving when a change is not fully implemented. This skill requires artifact and task completion checks to pass, ensuring incomplete changes remain active.

Related Skills

Explore More Software Engineering Skills→
shivrosshivros

openspec-archive-change

Archive completed changes in the experimental workflow using the openspec CLI.

Community
Intermediate
maxculen86maxculen86

sdd-archive

Merge delta specs into main specs and archive completed changes with dated reports.

Community
Advanced
rock-hurock-hu

openspec-archive-change

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

Community
Advanced
anssipanssip
26

openspec-archive-change

Archive completed OpenSpec changes into date-stamped folders.

Community
Advanced