openspec-archive-change

Archive completed OpenSpec changes with date-based naming and validation.

Updated Jun 4, 2025

Search Tags:#workflow #archive #openspec #change-management #artifact-status #delta-specs

Ready to run

npx skills add https://github.com/alexei-lexx/budget --skill openspec-archive-change-alexei-lexx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/alexei-lexx/budget/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/alexei-lexx/budget --skill openspec-archive-change-alexei-lexx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes after implementation to keep workflow history clean and auditable.

Core Features & Use Cases

Guarded archiving: move finished changes to an archive with date-based naming while preserving metadata and original structure.
Validation gates: verify artifact completion and task completion, optionally prompting before archiving.
Delta-spec synchronization: assess and optionally sync delta specs with main specs prior to archiving.
Audit-ready summaries: provide a final report detailing artifacts, tasks, and archive location for records.

Quick Start

Run the archive workflow to finalize a completed OpenSpec change and move it into the archive with a date-based 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 OpenSpec changes after implementation?▼

To archive completed OpenSpec changes, you run a workflow that validates artifact and task completion, optionally syncs delta specs, and moves finished changes to a date-based archive folder while preserving metadata and original structure.

What is the best way to keep OpenSpec workflow history clean and auditable?▼

Keeping OpenSpec workflow history auditable requires archiving finished changes with date-based naming and generating a final report detailing artifacts, tasks, and archive location for historical records.

How does delta-spec synchronization work before archiving OpenSpec changes?▼

Delta-spec synchronization assesses and optionally syncs delta specs with main specs prior to archiving, ensuring the primary workflow specifications are updated before the change artifacts are moved away.

Can I validate artifact and task completion before moving OpenSpec changes to the archive?▼

Yes, validation gates verify artifact completion and task completion before archiving, optionally prompting you interactively to confirm that all implementation requirements are fully satisfied.

Does OpenSpec archiving preserve metadata and original folder structure?▼

OpenSpec archiving preserves metadata and original structure by moving finished changes to an archive directory using date-based naming, ensuring the historical context of the change remains intact and auditable.

What limitations or precautions should I consider when archiving OpenSpec changes?▼

Limitations include ensuring all validation gates pass before archiving, as moving unfinished changes prematurely can break workflow history and compromise the audit trail of your delta specs.