openspec-archive-change

Archive completed changes with openspec CLI after completion checks.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/TranVanTienDat/barber-shop --skill openspec-archive-change-tranvantiendat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/TranVanTienDat/barber-shop/tree/main/.agent/skills/openspec-archive-change
Command: npx skills add https://github.com/TranVanTienDat/barber-shop --skill openspec-archive-change-tranvantiendat

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps in archiving completed changes in an experimental workflow, allowing users to finalize and store changes once implementation is complete.

Core Features & Use Cases

  • Archive Completed Changes: Finalize and archive changes after implementation.
  • Change Selection: Optionally specify a change name or select from available changes.
  • Completion Checks: Verify artifact and task completion status before archiving.
  • Delta Spec Sync: Optional sync of delta specs with main specs for archiving.
  • Archive Summary: Display summary of the archiving process, including the change name, schema, and archive location.

Quick Start

Use the archive_change command to finalize and archive a completed change. If needed, provide the change name as an argument.

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 in an openspec workflow, you use a command that checks artifact and task completion status before finalizing and storing the changes. This ensures only fully implemented changes are archived.

What is change archiving in experimental workflow management?

Change archiving in experimental workflow management is the process of finalizing and storing changes once implementation is complete. It verifies completion status and optionally syncs delta specs before moving changes to an archive location.

Do I need the openspec CLI to finalize and archive changes?

Yes, the openspec CLI is required to finalize and archive changes. The archiving process depends on the CLI for listing available changes, checking their status, and managing artifacts before completing the archival.

Can I sync delta specs with main specs before archiving a change?

Yes, you can optionally sync delta specs with main specs before archiving a change. This integrates incremental specification updates into the main specification set during the finalization process.

What happens if artifact and task completion checks fail before archiving?

If artifact and task completion checks fail, the archiving process prevents the change from being finalized. The system verifies that all necessary artifacts and tasks are complete before allowing the archival to proceed.

How do I select a specific change to archive from available changes?

To select a specific change to archive, you provide the change name as an argument to the archive command. If no name is provided, you can select from a list of available changes retrieved via the openspec CLI.