openspec-archive-change

Archive completed OpenSpec changes to a dated directory while preserving .openspec.yaml.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/ybenitezf/pi-github --skill openspec-archive-change-ybenitezf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/ybenitezf/pi-github/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/ybenitezf/pi-github --skill openspec-archive-change-ybenitezf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes to tidy up active workspace and preserve historical configurations for future reference and audits.

Core Features & Use Cases

  • Move completed change directories to archived location openspec/changes/archive/YYYY-MM-DD-openspec-archive-change consistently.
  • Preserve .openspec.yaml during move to archive.
  • Generate a clear summary including change name, schema, archive location, and sync status.

Quick Start

Archive a finished OpenSpec change by running the archive command with the change name, or omit to select from active changes.

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 for long-term storage?

To archive completed OpenSpec changes, the workflow moves the change directory to openspec/changes/archive/YYYY-MM-DD-openspec-archive-change after verifying all artifacts and tasks are complete via openspec status checks.

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

The .openspec.yaml file is preserved during the move to the archive directory, ensuring historical configurations and metadata remain intact for future reference and audits.

When should I archive an OpenSpec change instead of keeping it active?

You should archive an OpenSpec change when all artifacts and tasks are complete, the change has been implemented, and the delta specs are ready for long-term storage to tidy up the active workspace.

Does the OpenSpec archive process check task completion before moving files?

Yes, the OpenSpec archive process enforces checks via openspec status to confirm all artifacts and tasks are complete, prompting the user as required before moving the change directory to the archive path.

Can I sync delta specs when archiving a completed OpenSpec change?

Yes, the archiving workflow handles delta specs and provides optional syncing as needed during the move to the archive directory, followed by a summary of the sync status.