openspec-archive-change

Archive completed changes to openspec/changes/archive after verifying artifacts and tasks.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/canyangliunian/Agent-skills --skill openspec-archive-change-canyangliunian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/canyangliunian/Agent-skills/tree/main/ABS-Journal/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/canyangliunian/Agent-skills --skill openspec-archive-change-canyangliunian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed changes in the experimental workflow is essential to preserve a clean history, reduce clutter, and ensure reproducibility.

Core Features & Use Cases

  • Prompt change selection if the change name is not provided.
  • Validate artifact completion via openspec status and report any incomplete artifacts.
  • Validate task completion via tasks.md, counting incomplete items.
  • Assess delta-spec synchronization state and generate a unified summary before archiving.
  • Create the archive directory, move the change to openspec/changes/archive/YYYY-MM-DD-<name>, and preserve the .openspec.yaml alongside.
  • Display a concise archive summary including change name, schema, archive location, and sync status.
  • Warnings from artifacts or tasks do not block archiving; user confirmation is requested.

Quick Start

Initiate the archive by selecting a change name when prompted and follow the guided prompts to verify artifacts and tasks, optionally syncing delta specs before moving the change to archive.

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 OpenSpec while preserving metadata?

To archive completed changes in OpenSpec, the workflow moves the change folder to openspec/changes/archive/YYYY-MM-DD-<name> while preserving the .openspec.yaml metadata file. It ensures a clean project history and reproducibility by validating artifacts and tasks before relocation.

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

Archiving an OpenSpec change with incomplete tasks generates a warning but does not block the process. The workflow counts incomplete items in tasks.md, reports them in a unified summary, and requests user confirmation before proceeding with the archive relocation.

How does the OpenSpec archive workflow verify delta-spec synchronization?

The OpenSpec archive workflow assesses delta-spec synchronization state and generates a unified summary before archiving. It runs openspec status to check progress, validating both artifact completion and task completion to ensure all components are properly synced.

Can I automatically archive an OpenSpec change without specifying the name?

You cannot automatically archive without a name; the workflow prompts for change selection if the name is not provided. Once selected, it displays a concise archive summary including the change name, schema, archive location, and sync status.

When should I use the OpenSpec change archiving workflow in my automation pipeline?

Use the OpenSpec change archiving workflow when changes require artifact and task verification, delta-spec synchronization, and safe archiving. It reduces clutter in your active workspace by relocating verified changes to a dedicated archive directory.