openspec-archive-change

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

Archive completed openspec changes while preserving metadata and validating status.

Updated Dec 31, 2025

Search Tags:#automation #workflow #devops #versioning #archive #openspec #change-management

Ready to run

npx skills add https://github.com/rockdong/stock_for_cpp --skill openspec-archive-change-rockdong

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives a completed openspec change and moves it into a centralized archive.

Core Features & Use Cases

Automates the archival of completed openspec changes, including artifact and task status checks.
Performs delta-spec synchronization assessment when present and archives with a clear summary.
Preserves existing configuration and metadata (e.g., .openspec.yaml) during the move to archive.

Quick Start

Provide a change name to archive (or let the system prompt you to select one) and confirm archiving to complete the process.

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 openspec change and move it to a centralized location?▼

Archiving openspec changes requires validating artifact and task completion status. The workflow checks completion via openspec commands, assesses optional delta-spec synchronization, and preserves configuration metadata like .openspec.yaml during the centralized archival move.

What is the best way to finalize an openspec workflow and keep my change history organized?▼

Finalizing an openspec workflow requires archiving completed changes into a centralized repository. The process preserves configuration metadata like .openspec.yaml, assesses delta-spec synchronization, and generates a clear archival summary to maintain organized change history.

Does the openspec archival process check if all tasks and artifacts are completed before moving records?▼

Yes, the openspec archival process enforces status checks via openspec commands to validate artifact and task completion. It applies guardrails including user selection prompts to ensure only verified completed changes are moved into the centralized archive.

Can I sync delta specs when archiving changes in my devops versioning workflow?▼

Yes, you can sync delta specs during the change archiving process. The workflow performs delta-spec synchronization assessment when changes are present, allowing optional spec syncing before finalizing the archival record-keeping and metadata preservation.

Why does archiving an openspec change require preserving the .openspec.yaml configuration file?▼

Preserving the .openspec.yaml configuration file during archiving maintains existing environment settings and metadata integrity. This ensures the archived change retains its original context and configuration within the centralized archive for future reference.