openspec-archive-change

Archive completed changes after verifying artifacts and tasks with the openspec CLI.

1|Updated Feb 13, 2026

Search Tags:#workflow #gitops #archive #change management #openspec #spec sync

Ready to run

npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-archive-change-em-jones

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/em-jones/staccato-toolkit/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-archive-change-em-jones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed changes within the experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

Automated Archiving: Moves completed changes to a designated archive location.
Status Checks: Verifies artifact and task completion before archiving.
Spec Sync Assessment: Evaluates and optionally syncs delta specs before archiving.
Use Case: After implementing a new feature and testing all associated artifacts and tasks, use this Skill to formally archive the change, moving its associated files to the openspec/changes/archive directory.

Quick Start

Use the openspec-archive-change skill to archive the change named 'new-user-profile'.

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 OpenSpec?▼

To archive a completed change in OpenSpec, the skill verifies artifact and task completion, assesses delta specs, and moves the change directory to the openspec archive folder. This ensures a clean project history for finished workflows.

What is delta spec synchronization before archiving?▼

Delta spec synchronization evaluates and optionally syncs specification changes before archiving a completed workflow. This ensures the main specs reflect the latest updates before the change directory is moved to the archive.

Do I need the openspec CLI to archive a change?▼

Yes, you need the openspec CLI to archive a change because the skill requires it for status checks and artifact management. The CLI verifies that all tasks and artifacts are complete before moving the directory.

How to verify task and artifact completion before moving a change to the archive?▼

Verifying task and artifact completion before moving a change to the archive is handled automatically by checking the workflow status. The skill prevents archiving by moving the directory only after confirming all requirements are met.

Why does my completed change not move to the archive directory?▼

A completed change fails to move to the archive directory when artifact and task completion checks are not verified. The skill requires the openspec CLI to confirm status, ensuring incomplete changes are not archived prematurely.