openspec-archive-change

Archive completed changes to dated directories after validating tasks and delta specs.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/runecalico-ai/second_edition_spellbook --skill openspec-archive-change-runecalico-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/runecalico-ai/second_edition_spellbook/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/runecalico-ai/second_edition_spellbook --skill openspec-archive-change-runecalico-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed changes within an 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.
  • Delta Spec Sync: Assesses and optionally syncs delta specifications with main specifications.
  • Use Case: After successfully implementing and testing a new feature, use this Skill to formally archive the associated development changes, ensuring all related artifacts and tasks are accounted for.

Quick Start

Use the openspec-archive-change skill to archive the change named 'new-feature-x'.

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 an openspec workflow?

To archive completed changes, this Skill moves the change directory to a dated archive location. It validates artifact and task completion, assesses delta spec synchronization, and prompts for confirmation before proceeding.

What happens to delta specs when archiving a completed change?

When archiving a completed change, the Skill assesses delta spec synchronization with main specifications. It optionally syncs these delta specs using the openspec CLI to ensure project specifications remain consistent.

Does archiving a change require the openspec CLI?

Yes, archiving a change requires the openspec CLI. The Skill depends on the CLI to perform status checks for artifact and task completion validation and to handle potential delta spec synchronization.

How do I verify task completion before archiving a change?

You can verify task completion before archiving by running this Skill, which automatically performs status checks using the openspec CLI. It validates all associated artifacts and tasks to ensure everything is complete before moving the directory.

Can I review the archive process before the change directory is moved?

Yes, you can review the process because the Skill prompts for user confirmation before proceeding. It validates completion and assesses delta spec synchronization, then waits for your explicit approval to move the directory.

When should I archive a change in change management workflows?

You should archive a change after successfully implementing and testing a new feature. This ensures all related artifacts and tasks are accounted for and formally organizes the development changes into a dated archive location.