openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dianedef/ShipFlow --skill openspec-archive-change-dianedef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/dianedef/ShipFlow/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/dianedef/ShipFlow --skill openspec-archive-change-dianedef

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 directory.
  • Status Verification: Checks artifact and task completion before archiving.
  • Delta Spec Sync: Assesses and optionally syncs delta specifications with main specs.
  • Use Case: After successfully implementing and testing a new feature, use this Skill to formally archive the associated change, marking it as complete and organized.

Quick Start

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

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 experimental workflow?

To archive completed changes, you can use a workflow skill that verifies artifact and task completion status, syncs delta specifications, and moves the change directory to a designated archive location. This ensures a clean and organized project history.

What is delta spec sync and when do I need it during change archiving?

Delta spec sync assesses and optionally merges delta specifications with main specs before archiving. You need it when finalizing an experimental change to ensure your main specifications reflect the completed updates.

How do I verify task completion before archiving a change?

Verifying task completion before archiving involves checking artifact and task completion status using the openspec CLI. The archiving process requires these status checks to pass before moving the change directory.

Does the openspec-archive-change process require any specific CLI tools?

Yes, archiving changes requires the openspec CLI for performing status checks and listing available changes. You need this command-line interface installed to verify completion and execute the archiving workflow.

Can I move an incomplete experimental change to the archive directory?

No, you cannot move incomplete changes because the process verifies artifact and task completion status before archiving. It ensures only successfully implemented and tested features are formally archived.

What is the best way to organize completed experimental changes in version control?

The best way to organize completed experimental changes is to use an automated archiving skill that moves finished change directories to a designated archive location after verifying completion and syncing specifications, maintaining a clean project history.