openspec-archive-change

Archive completed OpenSpec changes into date-prefixed directories with artifact validation.

54|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/mrclrchtr/SuPi --skill openspec-archive-change-mrclrchtr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/mrclrchtr/SuPi/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/mrclrchtr/SuPi --skill openspec-archive-change-mrclrchtr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed OpenSpec change after implementation to preserve history and enable audit trails.

Core Features & Use Cases

  • Archiving completed changes to openspec/changes/archive with a date-prefixed directory.
  • Preserving associated artifacts and delta/spec synchronization status for auditability.
  • Guardrails to prompt for change selection, validate artifacts and tasks, and optionally syncing delta specs before archiving.

Quick Start

Provide the change name when prompted and run the archive workflow to move openspec/changes/<name> to openspec/changes/archive/YYYY-MM-DD-<name>, then review the 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 to preserve an audit trail?

To archive completed OpenSpec changes, you move the change directory to a date-prefixed archive folder. This preserves associated artifacts and delta spec synchronization status, ensuring a complete audit trail for your version control workflow.

What is the directory structure used when archiving OpenSpec changes?

Archiving OpenSpec changes uses a date-prefixed directory structure. The workflow moves the original change folder into openspec/changes/archive/YYYY-MM-DD-<name> to maintain chronological history and artifact traceability.

How do I finalize an OpenSpec change and verify artifact completeness before archiving?

Finalizing an OpenSpec change involves a guided workflow that validates artifact completeness and task status. Guardrails prompt you to verify all associated artifacts and optionally sync delta specs before moving the change to the archive.

Can I sync delta specs before moving a completed OpenSpec change to the archive?

Yes, you can sync delta specs before archiving. The workflow includes optional guardrails to synchronize delta specs, ensuring the main specifications reflect the implemented changes before the completed OpenSpec change is archived.

Do I need to manually validate task status before archiving OpenSpec changes?

No, manual validation is not required. The archive workflow automatically checks artifact and task status, applying guardrails to ensure an OpenSpec change is fully completed and verified before moving it to the archive directory.

When should I use an automated workflow for OpenSpec change management?

You should use an automated workflow for OpenSpec change management when finalizing implementations. It ensures consistent artifact verification, delta spec synchronization, and accurate audit trail recording without manual file operations.