openspec-archive-change

Archive completed experimental changes into date-stamped folders after verification.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill openspec-archive-change-inspedralbes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW/tree/main/prj-entrades-nou/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill openspec-archive-change-inspedralbes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow by finalizing and relocating them to a dedicated archive with a date-stamped folder, ensuring traceability and reproducibility.

Core Features & Use Cases

  • End-to-end archiving of changes after implementation, including artifact and task status checks.
  • Delta-spec assessment and optional synchronization with main specs to keep records aligned.
  • Clear, auditable archive process with guardrails and warnings for incomplete artifacts or tasks.

Quick Start

Archive a completed change by selecting the change, verify artifacts and tasks, assess delta specs and optionally sync, then move the change into the archive with a date-stamped folder.

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 change management workflows with delta specs?

Archiving completed change management workflows involves verifying artifacts and task statuses, assessing delta specs, optionally synchronizing main specs, then moving the change into a date-stamped archive folder to preserve auditable history.

What is the best way to finalize implementation artifacts after a workflow change?

Finalizing implementation artifacts requires running artifact and task checks via openspec commands, evaluating delta specs against main specs, and safely relocating the verified change folder to a dedicated archive with a date tag.

Can I sync delta specs with main specs before archiving an openspec change?

Yes, you can optionally synchronize delta specs with main specs during the archiving process. This assessment step ensures your records remain aligned before the change is safely moved into the final archive.

What happens if I try to archive incomplete tasks or unverified artifacts in openspec?

Archiving incomplete tasks or unverified artifacts triggers built-in guardrails and warnings. The Skill operates across artifact verification and task status checks to ensure records are accurate before allowing the safe move operation.

Do I need any dependencies to use the openspec archive change Skill?

No dependencies are required to use the openspec archive change Skill. It operates independently using interactive change selection and openspec commands to verify artifacts and safely move changes into a date-stamped archive.

Why does the archive process include a date-stamped folder and preserved yaml file?

The date-stamped folder and preserved .openspec.yaml file ensure traceability and reproducibility. This archiving mechanism maintains an auditable history by tagging the archive with a date and keeping the original configuration intact.