openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts, tasks, and specification synchronization.

15|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/mahoushoujyo-eee/eshell --skill openspec-archive-change-mahoushoujyo-eee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/mahoushoujyo-eee/eshell/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/mahoushoujyo-eee/eshell --skill openspec-archive-change-mahoushoujyo-eee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps finalize completed OpenSpec changes without accidentally archiving unfinished work or overlooking unsynchronized specifications.

Core Features & Use Cases

  • Change Selection: Lists active changes and prompts the user to explicitly choose one when no change name is provided.
  • Completion Checks: Verifies artifact and task status, clearly warns about incomplete work, and requests confirmation before proceeding.
  • Specification Synchronization: Reviews delta specifications against main specifications and offers synchronization before archiving.
  • Safe Archiving: Creates dated archive paths, prevents overwriting existing archives, preserves change metadata, and reports the final outcome.
  • Use Case: After implementing a feature, use this Skill to verify its OpenSpec artifacts and tasks, sync any pending specification updates, and move the completed change into a dated archive.

Quick Start

Ask the OpenSpec workflow to archive the completed change named "<change-name>" after checking its artifacts, tasks, and specification synchronization state.

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 safely?

To archive OpenSpec changes safely, use a workflow that verifies artifact and task completion, prompts for explicit confirmation on unfinished work, syncs delta specifications, and moves files into dated archive directories without overwriting existing archives.

What happens if I try to archive OpenSpec tasks that are incomplete?

When archiving incomplete OpenSpec tasks, the workflow checks artifact and task status, clearly warns about the unfinished work, and requires your explicit confirmation before proceeding with the archival to prevent accidental data loss.

Does OpenSpec archival synchronize delta specifications with main specifications?

Yes, OpenSpec archival reviews delta specifications against main specifications and offers synchronization before moving the completed change into a dated archive directory to ensure all documents are up to date.

Do I need the OpenSpec CLI to archive completed changes?

Yes, you need the OpenSpec CLI installed to archive completed changes, as the workflow requires it to list active changes, check completion status, and execute the file operations for safe archival.

How are archived OpenSpec changes organized to prevent overwriting?

Archived OpenSpec changes are organized into dated archive paths, which prevents overwriting existing archives, preserves change metadata, and reports the final outcome of the archival process.

Can I select a specific OpenSpec change to archive without providing a name?

If no change name is provided, the workflow lists all active OpenSpec changes and prompts you to explicitly choose one, ensuring you archive the correct feature implementation safely.