openspec-archive-change

Archive completed OpenSpec changes under date-stamped directories after verifying artifacts and tasks.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/oalansilva/crypto --skill openspec-archive-change-oalansilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/oalansilva/crypto/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/oalansilva/crypto --skill openspec-archive-change-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables teams to finalize and archive OpenSpec changes once implementation is complete, preserving provenance and keeping an organized history.

Core Features & Use Cases

  • Prompt-driven change selection: If you don't provide a change name, the tool asks you to choose from active changes.
  • Artifact and task verification: Checks that all artifacts are done and tasks are completed before archiving.
  • Delta spec sync assessment: Evaluates any delta specs against main specs and suggests syncing if needed.
  • Date-stamped archiving: Moves the change directory into an archive location named with the current date, preserving metadata.
  • Clear summary output: Reports the archive details, including whether syncing occurred and any warnings.

Quick Start

Provide a change name to begin the archival process, or let the tool prompt you to select one, then proceed through the 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 while preserving metadata and provenance?

To archive OpenSpec changes, the tool moves the completed change directory into a date-stamped archive location. This process preserves metadata and ensures an organized history by verifying artifact and task completion before finalizing the archive.

What happens if I try to archive an OpenSpec change with incomplete tasks or artifacts?

When archiving an OpenSpec change with incomplete tasks or artifacts, the tool enforces guardrails by reporting warnings. It checks for artifact and task completion during the process and provides a clear summary output detailing any incomplete items.

How does delta spec synchronization work when finalizing an OpenSpec change?

During OpenSpec change archival, the tool assesses delta specs against main specs to evaluate synchronization. It suggests syncing if needed and includes whether synchronization occurred within the final archive summary report.

Can I select a specific OpenSpec change to archive, or does the tool require a name upfront?

You can provide a change name to begin the archival process directly. If you do not provide a name, the tool uses prompt-driven change selection, asking you to choose from the list of currently active changes before proceeding.

When should I use an automated workflow to archive change management artifacts?

You should use an automated archive workflow when an OpenSpec change has been fully implemented and validated. It ensures artifact and task verification are complete, assesses delta spec sync, and securely archives the finalized project state.

Are there limitations to archiving OpenSpec changes using this automated workflow?

A key limitation is that the workflow requires all implementation and validation to be complete before archiving. Although it can archive with incomplete artifacts or tasks by issuing warnings, it is designed for finalizing fully completed change management processes.