openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: SinesysTech

Archive completed openspec changes after verifying status and delta spec sync.

Updated Aug 23, 2026

Search Tags:#workflow #version control #archive #change management #openspec #spec sync

Ready to run

npx skills add https://github.com/SinesysTech/diegobarbosa-os --skill openspec-archive-change-sinesystech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/SinesysTech/diegobarbosa-os/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/SinesysTech/diegobarbosa-os --skill openspec-archive-change-sinesystech

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you finalize and archive 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 Verification: Checks artifact and task completion before archiving.
Delta Spec Sync: Assesses and optionally syncs delta specifications with main specifications.
Use Case: After implementing a new feature and testing it thoroughly, use this Skill to archive the development work, making it clear that the change is complete and ready for historical reference.

Quick Start

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

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

You archive completed changes by moving the change directory to an archive location. This Skill verifies artifact and task completion, assesses delta spec synchronization, and prompts for confirmation before proceeding.

Does archiving a change verify if task completion is done?▼

Yes, archiving a change verifies task completion status. It checks both artifact and task completion before moving the directory to ensure only finished changes get archived.

What is delta spec synchronization when finalizing a change?▼

Delta spec synchronization assesses whether delta specifications are aligned with main specifications. This Skill evaluates sync status and optionally syncs them before archiving the completed change.

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

Yes, you need the openspec CLI to archive a completed change. It is required for performing status checks and listing available changes before the archiving process proceeds.

Can I sync main specifications automatically during change archiving?▼

You can optionally sync main specifications during change archiving. The Skill assesses delta spec synchronization and prompts for user confirmation before proceeding with the archive operation.

Why is user confirmation required before moving a directory to the archive?▼

User confirmation is required before moving a directory to the archive to prevent accidental data loss. It ensures the verified artifact and task completion statuses meet your approval before finalizing.