openspec-archive-change

Archive completed OpenSpec changes into dated folders with validation.

3|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/g1331/AutoRouter --skill openspec-archive-change-g1331
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/g1331/AutoRouter/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/g1331/AutoRouter --skill openspec-archive-change-g1331

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives completed OpenSpec changes to preserve history, enforce guardrails, and prevent drift by moving finalized work into a date-stamped archive.

Core Features & Use Cases

  • Automated archival: Move a completed change from openspec/changes/<name> to openspec/changes/archive/YYYY-MM-DD-<name> while preserving .openspec.yaml.
  • Artifact and task validation: Check artifact completion via openspec status and count incomplete tasks in tasks.md, prompting before archiving.
  • Delta spec synchronization: Assess delta specs and optionally sync with main specs before archiving; provide a consolidated summary for user confirmation.
  • Audit-ready summaries: Generate a concise archival summary including change name, schema used, archive location, and whether syncing occurred.

Quick Start

Archive a completed change by name to move it into the archive folder with a date stamp.

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 using a date-stamped folder?

To archive completed OpenSpec changes, the skill moves finalized work from openspec/changes/<name> to openspec/changes/archive/YYYY-MM-DD-<name>. It preserves the .openspec.yaml configuration file and ensures the destination path exists before relocation.

Can I archive OpenSpec changes if incomplete artifacts or tasks still exist?

Archiving OpenSpec changes with incomplete artifacts or tasks triggers a user prompt before proceeding. The skill checks artifact completion via openspec status and counts incomplete tasks in tasks.md to enforce guardrails and prevent drift.

Does OpenSpec archival synchronize delta specs with main specs?

OpenSpec archival assesses delta specs and optionally syncs them with main specs before archiving. It provides a consolidated summary for user confirmation, ensuring the final archived state reflects the synchronized changes.

What is included in the OpenSpec change archival summary?

The OpenSpec change archival summary includes the change name, schema used, archive location, and whether delta spec syncing occurred. This audit-ready summary ensures historical preservation and tracks the finalization process.

How do I finalize experimental OpenSpec workflows that generate change artifacts?

Finalizing experimental OpenSpec workflows involves running finalization checks on generated change artifacts and tasks. The skill safely archives completed work into a dated folder, enforcing validation prompts for any incomplete items.

Why should I use a dedicated archival process for OpenSpec changes?

Using a dedicated archival process for OpenSpec changes preserves project history, enforces completion guardrails, and prevents configuration drift. It moves finalized work into a date-stamped archive while validating tasks and synchronizing delta specs.