skills.rest
SimplifyMyCloud
SimplifyMyCloudOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts and tasks.

Updated Jan 30, 2026
Search Tags:#automation#workflow#archival#archive#openspec#change-management#delta-spec
One-click install
npx skills add https://github.com/SimplifyMyCloud/gcp-bq-no-egress-dashboard-poc --skill openspec-archive-change-simplifymycloud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/SimplifyMyCloud/gcp-bq-no-egress-dashboard-poc/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/SimplifyMyCloud/gcp-bq-no-egress-dashboard-poc --skill openspec-archive-change-simplifymycloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed OpenSpec change.

Core Features & Use Cases

  • Prompts for change selection when not provided.
  • Checks artifact completion and task status.
  • Compares delta specs with main specs and optionally syncs.
  • Archives the change to the designated archive directory with metadata preservation.
  • Presents a clear summary of the operation.

Quick Start

Provide the change name when prompted, and the tool will archive the change to openspec/changes/archive/YYYY-MM-DD-<name>.

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

To archive a completed OpenSpec change, you provide the change name to prompt for selection and verify artifact and task completion, then safely archive the change to the designated archive directory while preserving metadata.

What is the process for syncing delta specs with main specs before archiving?▼

Syncing delta specs involves comparing delta specs with main specs and optionally syncing via openspec, ensuring all changes are reconciled before the change is safely archived to the archive directory with metadata preserved.

When should I archive OpenSpec changes using change-management automation?▼

You should archive OpenSpec changes when a change has been fully implemented and you need to verify artifact and task completion, optionally sync delta specs, and preserve metadata in a designated archive directory.

How do I verify artifact and task completion before archiving an OpenSpec change?▼

Verifying artifact and task completion is handled by checking artifact completion and task status during the archival workflow, ensuring only fully implemented changes are archived to the openspec/changes/archive/YYYY-MM-DD-<name> directory.

Can I use OpenSpec archiving without manually syncing delta specs?▼

Yes, delta spec syncing is optional during OpenSpec archiving; the tool compares delta specs with main specs and allows you to optionally sync via openspec before safely archiving the completed change with metadata preservation.

What metadata is preserved when archiving an OpenSpec change to the archive directory?▼

When archiving an OpenSpec change to the designated archive directory at openspec/changes/archive/YYYY-MM-DD-<name>, the tool preserves the change's associated metadata while presenting a clear summary of the operation.

Related Skills

Explore More Software Engineering Skills→
DraculaboDraculabo
2.0k

openspec-archive-change

Archive completed OpenSpec changes with artifact checks and date-based naming.

Community
Advanced
RyanCallahan312RyanCallahan312

openspec-archive-change

Archive completed OpenSpec changes to an auditable directory with metadata.

Community
Advanced
mrp4stenmrp4sten
3

sdd-archive

Merge delta specs into main specs and archive changes with ISO date paths.

Community
Advanced
MiDouTechMiDouTech

openspec-archive-change

Archive completed openspec changes into date-prefixed directories after verification.

Official
Advanced