openspec-archive-change

Archive completed changes in an OpenSpec workflow with status checks.

Updated Aug 23, 2026

Search Tags:#workflow management #developer tool #OpenSpec #change archiving #specification syncing

Ready to run

npx skills add https://github.com/MattJColes/macols-configs --skill openspec-archive-change-mattjcoles

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/MattJColes/macols-configs/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/MattJColes/macols-configs --skill openspec-archive-change-mattjcoles

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of archiving completed changes in the OpenSpec workflow, allowing users to finalize and archive changes after implementation is complete.

Core Features & Use Cases

Change Archiving: Automates the archiving of completed changes in the OpenSpec workflow.
User Selection: Allows users to select the change they wish to archive.
Status Checks: Checks the completion status of artifacts and tasks before archiving.
Spec Syncing: Optionally syncs delta specs with the main specs before archiving.
Use Case: Ideal for developers and system administrators who need to maintain a clean and organized OpenSpec workflow by archiving completed changes.

Quick Start

Archive the latest change in your OpenSpec workflow using the 'archive-change' skill.

Frequently Asked Questions about openspec-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate change archiving in an OpenSpec workflow?▼

Automate change archiving in OpenSpec by selecting completed changes, verifying artifact and task completion statuses, and optionally syncing delta specs with main specs before finalizing the archive.

When should I archive completed changes in OpenSpec?▼

Archive completed changes in OpenSpec after implementation is finished and all associated artifacts and tasks are marked complete, ensuring your workflow remains clean and organized for future development cycles.

Do I need the OpenSpec CLI to archive completed changes?▼

Yes, archiving completed changes requires the OpenSpec CLI and appropriate permissions to access, modify, and sync delta specifications within your existing workflow environment.

Can I sync delta specs with main specs before archiving changes?▼

Yes, you can optionally sync delta specs with main specs before archiving changes, ensuring all specification updates are consolidated and finalized during the change archiving process.

What happens if artifacts or tasks are not complete when archiving OpenSpec changes?▼

The archiving process checks the completion status of artifacts and tasks before proceeding, preventing incomplete changes from being archived and ensuring only fully implemented changes are finalized.

Best way to maintain a clean OpenSpec workflow after implementation?▼

Archive completed changes using automated change archiving to finalize implementations, sync delta specs, and remove finished tasks from the active workflow, keeping your development environment organized.