openspec-archive-change

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

1|Updated May 22, 2022
One-click install
npx skills add https://github.com/jeffbalagosa/pick-or-shuffle --skill openspec-archive-change-jeffbalagosa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/jeffbalagosa/pick-or-shuffle/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/jeffbalagosa/pick-or-shuffle --skill openspec-archive-change-jeffbalagosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed experimental changes to the persistent archive after implementation, ensuring artifacts and tasks are complete and preserving delta specs if any.

Core Features & Use Cases

  • Auto-creates an archive directory at openspec/changes/archive if missing and moves the change directory there with a date-based name.
  • Validates artifacts via openspec status to block incomplete items, checks task completion in tasks.md, and assesses delta specs for synchronization.
  • Preserves important metadata like .openspec.yaml during relocation and provides a final summary of actions.

Quick Start

Provide the change name to archive, or let me select from active changes, then confirm artifacts and tasks before archiving.

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 safely?

To archive completed openspec changes, the workflow validates artifact status and task completion, syncs delta specs, and relocates the change directory to a persistent archive with date-based naming while preserving .openspec.yaml metadata.

What is the process for preserving delta specs during change archival?

Delta spec preservation during change archival involves assessing synchronization status before moving the directory. The workflow ensures delta specs are synced and safely relocated alongside the change artifacts into the archive folder.

How does openspec status validation block incomplete change archival?

Openspec status validation blocks incomplete change archival by checking artifacts and tasks.md completion. If validation fails, the workflow prevents relocating the change directory to ensure only fully implemented experimental changes are archived.

Can I infer the change name automatically when archiving experimental changes?

Yes, you can infer the change name automatically. The workflow supports optional change name inference, allowing you to select from active changes if a specific name is not provided for the archival process.

What happens to the .openspec.yaml file when relocating a change to the archive?

When relocating a change to the archive, the .openspec.yaml file is preserved. The safe relocation process ensures important metadata remains intact during the move to the auto-created openspec/changes/archive directory.