skills.rest
contenido-wq
contenido-wqCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed openspec changes after validating artifacts and tasks.

Updated May 12, 2026
Search Tags:#workflow#CLI automation#archive#change management#openspec#spec sync#artifact status
One-click install
npx skills add https://github.com/contenido-wq/aivi_core --skill openspec-archive-change-contenido-wq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/contenido-wq/aivi_core/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/contenido-wq/aivi_core --skill openspec-archive-change-contenido-wq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you finalize an implemented experimental change by archiving the change folder only after checking artifact and task completion status, and optionally syncing delta specs to the main specs.

Core Features & Use Cases

  • Change finalization with validation: Lists available active changes for selection, checks artifact completion via openspec status, and warns about incomplete artifacts or tasks before archiving.
  • Delta spec synchronization assessment: Detects delta specs in openspec/changes/<name>/specs/, compares them to corresponding main specs, and presents a combined summary before you choose whether to sync.
  • Safe archival with guardrails: Moves openspec/changes/<name> into openspec/changes/archive with a date-stamped directory name, and prevents overwriting an existing archive target.

Quick Start

Archive a completed change after implementation by asking the assistant to run openspec-archive-change for the specified change name, or tell it to infer the change from context if no name is provided.

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 openspec workflow changes safely?▼

Archiving completed openspec changes involves validating artifact and task completion via openspec status, optionally syncing delta specs to main specs, and then moving the change directory into openspec/changes/archive with a date-stamped name.

How does delta spec synchronization work when finalizing an openspec change?▼

Delta spec synchronization detects specs in openspec/changes/<name>/specs/, compares them against corresponding main specs, and presents a combined summary so you can choose whether to sync before archiving the change.

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

Yes, you need the openspec CLI to archive changes because the process uses openspec list and openspec status JSON parsing to check artifact and task completion before moving the folder.

What happens if I try to archive an openspec change with incomplete tasks or artifacts?▼

If artifacts or tasks are incomplete, the archiving process warns you about the missing completion checks before proceeding, ensuring you do not accidentally finalize an unfinished experimental workflow change.

Can I prevent overwriting an existing archived openspec change?▼

Yes, safe archival guardrails prevent overwriting an existing archive target by moving openspec/changes/<name> into openspec/changes/archive using a date-stamped directory name while preserving the .openspec.yaml configuration.

Related Skills

Explore More Software Engineering Skills→
ywh0606ywh0606

opsx-verify

Verify OpenSpec changes for completion and readiness before archiving.

Community
Intermediate
ilazinessilaziness
6

openspec-archive-change

Archive completed OpenSpec changes after validating tasks and syncing delta specs.

Community
Advanced
kaishinkaishin
10

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and syncing delta specs.

Community
Advanced
belingudbelingud
30

openspec-archive-change

Archive completed OpenSpec changes with verified artifacts and delta specs.

Community
Advanced