openspec-archive-change

Archive validated openspec changes into dated archive folders with metadata.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/lz-freedom/polybull-stock-helper --skill openspec-archive-change-lz-freedom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/lz-freedom/polybull-stock-helper/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/lz-freedom/polybull-stock-helper --skill openspec-archive-change-lz-freedom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in an experimental workflow to preserve artifacts and project history.

Core Features & Use Cases

  • Archive completed changes after validation to prevent rework and keep the workflow clean.
  • Compare delta specs with main specs and optionally sync before archiving.
  • Preserve metadata and artifacts while relocating the change to an archive folder.

Quick Start

  1. Ensure there is a target change to archive. If unsure, list available changes with openspec list --json and confirm the one to archive.
  2. Run the archive operation to move the change to openspec/changes/archive/YYYY-MM-DD-<change-name>.
  3. Verify the archived location and artifact references in the archive.

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 project history?

To archive completed openspec changes, run the archive operation to move validated changes into openspec/changes/archive/YYYY-MM-DD-<change-name>, preserving metadata and artifact references. It enforces mandatory change selection and checks artifact completion before safely relocating the folder.

What happens to delta specs when archiving an openspec change?

When archiving an openspec change, the workflow compares delta specs against main specs. You can optionally sync these delta specs with main specs before the change is moved to the archive folder, ensuring project specifications remain consistent and up to date.

Why does the openspec archive workflow require artifact completion checks?

Artifact completion checks are required during the openspec archive workflow to prevent rework and keep the workflow clean. By verifying artifact completion and validating task checks beforehand, the system ensures only fully completed changes are archived, preserving accurate project history.

Do I need to manually select a change before archiving it with openspec?

Yes, you must select a target change before archiving it with openspec. The workflow enforces mandatory change selection when one is missing. You can list available changes using openspec list --json to identify and confirm the specific change you intend to archive.

Can I verify artifact references after relocating an openspec change to the archive?

Yes, after relocating an openspec change to the archive folder, you can verify the archived location and its artifact references. The workflow safely moves the change while preserving metadata, allowing you to confirm that all project artifacts remain intact and accessible.