openspec-archive-change

Archive completed OpenSpec changes into date-stamped folders.

26|1|Updated May 2, 2022

Search Tags:#automation #workflow #artifacts #archive #openspec #change-management #delta-specs

Ready to run

npx skills add https://github.com/anssip/passlane --skill openspec-archive-change-anssip

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/anssip/passlane/tree/main/.pi/skills/openspec-archive-change
Command: npx skills add https://github.com/anssip/passlane --skill openspec-archive-change-anssip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed OpenSpec changes to preserve artifacts, tasks, and history while keeping the working directory organized.

Core Features & Use Cases

Prompts for change selection if no name is provided, ensuring deliberate archiving decisions.
Validates artifact completion and task status before archiving, with warnings but without blocking.
Assesses delta specs and optionally syncs with main specs to keep references up to date.
Creates a date-stamped archive directory under openspec/changes/archive and preserves .openspec.yaml with the archived change.
Provides a clear summary of what happened, including archive location and any warnings.

Quick Start

Archive a completed OpenSpec change by moving it to 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 changes in my OpenSpec workflow?▼

To archive completed OpenSpec changes, you move them to a date-stamped directory under openspec/changes/archive. This process preserves artifacts, tasks, and configuration files while keeping your working directory organized.

What happens to delta specs when I archive an OpenSpec change?▼

When archiving an OpenSpec change, the workflow assesses delta specs and optionally syncs them with main specs. This ensures references remain up to date before the change is safely moved to the archive folder.

Does OpenSpec archiving block if artifacts are incomplete or tasks are unfinished?▼

OpenSpec archiving does not block if artifacts or tasks are incomplete. The workflow validates artifact completion and task status, issuing warnings to notify you of pending items without halting the archiving process.

How does OpenSpec preserve configuration files during change archiving?▼

OpenSpec preserves configuration files by retaining the .openspec.yaml file within the archived change folder. This ensures the change's original settings and metadata remain intact inside the date-stamped archive directory.

Can I archive multiple OpenSpec changes at once without specifying names?▼

You cannot archive changes without deliberate selection, as the workflow prompts for a change name if none is provided. This ensures you explicitly choose which specific OpenSpec change to archive.

Why do I need to archive OpenSpec changes across development cycles?▼

You need to archive OpenSpec changes to maintain project history and artifact synchronization across development cycles. It moves completed work to a date-based archive, ensuring your active working directory stays clean.