openspec-archive-change

Archive completed openspec changes with artifact and task status checks.

14|1|Updated May 6, 2026
One-click install
npx skills add https://github.com/wzyxdwll/ccgx-workflow --skill openspec-archive-change-wzyxdwll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/wzyxdwll/ccgx-workflow/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/wzyxdwll/ccgx-workflow --skill openspec-archive-change-wzyxdwll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving a finalized change in an experimental workflow ensures preservation, traceability, and a clean project history.

Core Features & Use Cases

  • Change archiving: Move completed openspec changes to an archive with date-stamped naming.
  • Status checks: Verify artifact and task completion before archiving.
  • Delta spec sync assessment: Compare delta specs against main specs and optionally synchronize before archiving.
  • Audit trail: Provide a summarized report of the archive, including schema, location, and whether specs were synced.

Quick Start

Supply the change name and let the skill archive it after confirming artifacts and tasks are complete.

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 a completed change in an openspec workflow?

To archive a completed change in an openspec workflow, you supply the change name so the skill can verify artifact and task completion, compare delta specs, perform the archive, and present a summary. This ensures safe and transparent finalization.

What is delta spec synchronization during change archiving?

Delta spec synchronization during change archiving is the process of comparing delta specs against main specs and optionally updating the main specs before finalizing. This ensures your project history remains consistent and traceable when you archive a change.

How do artifact and task status checks work before archiving a change?

Artifact and task status checks work by verifying that all related artifacts and tasks are fully completed before allowing a change to be archived. This validation step prevents incomplete work from entering your archived project history.

Does change archiving require delta specs to be synced with main specs?

Change archiving does not strictly require delta specs to be synced with main specs, but it assesses and optionally synchronizes them before archiving. This provides an audit trail showing whether specs were synced during the process.

What is included in the audit trail when archiving a change?

The audit trail included when archiving a change provides a summarized report detailing the schema, the storage location, and whether delta specs were synced. This ensures traceability and a clean project history for your finalized workflow.