skills.rest
yuanhsunliu
yuanhsunliuCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed changes into openspec/changes/archive with date-prefixed names.

Updated Aug 23, 2026
Search Tags:#workflow#cli#archive#openspec#change-management#delta-spec#artifact-status
One-click install
npx skills add https://github.com/yuanhsunliu/dashboard-layout-editor-ui --skill openspec-archive-change-yuanhsunliu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/yuanhsunliu/dashboard-layout-editor-ui/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/yuanhsunliu/dashboard-layout-editor-ui --skill openspec-archive-change-yuanhsunliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow once implementation is finished, ensuring an auditable history and a clean repository state.

Core Features & Use Cases

  • Prompt-based selection of changes to archive when multiple options exist.
  • Comprehensive checks of artifact completion and task status before archiving.
  • Delta-spec synchronization assessment and optional realignment prior to archival.
  • Safe, date-prefixed archiving into openspec/changes/archive with a preserved .openspec.yaml.

Quick Start

Archive a completed change by selecting a change, verify its artifacts and tasks, assess delta-spec synchronization, archive the change to openspec/changes/archive, and display a summary

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 workflow changes without losing track of artifacts?▼

To archive completed changes, the system checks artifact completion, reviews task status, and assesses delta-spec synchronization, then moves the change directory to openspec/changes/archive with a date-prefixed name while preserving the .openspec.yaml file for auditable history.

What happens to delta-spec synchronization when archiving a change?▼

Delta-spec synchronization is assessed during the archival process, and optional realignment can be performed prior to moving the change directory to the archive, ensuring the repository state remains consistent and clean.

When should I archive a change in the change-management workflow?▼

You should archive a change in the change-management workflow after implementation is completely finished, which means all artifacts are complete, task statuses are reviewed, and delta-spec synchronization has been assessed and optionally realigned.

Can I select which change to archive when multiple completed changes exist?▼

Yes, when multiple completed changes exist, the archival process uses prompt-based selection to let you choose which specific change directory to verify and move into the date-prefixed archive path under openspec/changes/archive.

What checks are performed before a change is moved to the archive?▼

Before archiving, the system performs comprehensive checks of artifact completion, reviews task status, and assesses delta-spec synchronization, prompting for confirmation prior to moving the change directory and reporting a final summary.

Related Skills

Explore More Software Engineering Skills→
lbrlabslbrlabs
9

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with metadata preservation.

Official
Advanced
xiayu519xiayu519
63

openspec-archive-change

Archive completed OpenSpec changes to the archive directory after validation gates pass.

Community
Advanced
aniweianiwei

openspec-archive-change

Archive completed openspec changes into date-based folders via the openspec CLI.

Community
Advanced
sundaiclawsundaiclaw
7

openspec-archive-change

Archive completed OpenSpec changes with artifact and delta-spec checks.

Community
Advanced