openspec-archive-change

Archive completed openspec changes into date-based folders with validation and syncing checks.

273|270|Updated Jun 30, 2025
One-click install
npx skills add https://github.com/LIDR-academy/AI4Devs-LTI-extended --skill openspec-archive-change-lidr-academy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/LIDR-academy/AI4Devs-LTI-extended/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/LIDR-academy/AI4Devs-LTI-extended --skill openspec-archive-change-lidr-academy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the archival of completed openspec changes after implementation, preventing confusion and ensuring a consistent record of changes archived for reference and auditing.

Core Features & Use Cases

  • Automated validation of artifact completion and task status before archiving.
  • Delta-spec synchronization assessment and optional syncing guidance.
  • Archive to openspec/changes/archive/YYYY-MM-DD-<name> while preserving existing metadata and structure.
  • Use Case: When a change is fully implemented and verified, archive it to maintain a clean workspace and enable future retrieval.

Quick Start

Run the archive workflow to move the selected change into the archive folder and review the generated 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 openspec changes automatically?

To archive completed openspec changes automatically, run this Skill to validate artifact and task status, reconcile delta-specs, and move the change into a date-based archive folder while returning a summary with syncing status and warnings.

What is the process for delta-spec reconciliation before archiving?

Delta-spec reconciliation during archival involves assessing delta-spec synchronization status and optionally providing syncing guidance to resolve discrepancies before the completed change is safely moved into the openspec archive directory.

When should I archive an openspec change in the workflow?

You should archive an openspec change when it is fully implemented and verified, ensuring artifact completion and task status checks pass so you can maintain a clean workspace and enable future retrieval for auditing.

Does the archival workflow check artifact completion and task status?

Yes, the archival workflow performs automated validation of artifact completion and task status before archiving, preventing confusion by ensuring only fully implemented changes are moved into the openspec/changes/archive directory.

Can I preserve existing metadata when archiving delta-specs?

Yes, archiving delta-specs preserves existing metadata and structure while moving the completed change into an automatically generated date-based folder at openspec/changes/archive/YYYY-MM-DD-<name>.

What warnings should I look for when archiving an openspec change?

When archiving an openspec change, review the generated summary for warnings related to delta-spec synchronization status, incomplete artifacts, or task validation issues that might prevent a clean archival process.