openspec-archive-change

Archive completed openspec changes into openspec/changes/archive with status checks.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/chuangkevin/project-bridge --skill openspec-archive-change-chuangkevin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/chuangkevin/project-bridge/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/chuangkevin/project-bridge --skill openspec-archive-change-chuangkevin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in openspec workflows to finalize and preserve implementation records.

Core Features & Use Cases

  • Automated archival of finalized changes after implementation.
  • Enforces artifact completion with status checks before archiving.
  • Performs delta-spec sync assessment and prompts for optional syncing prior to archive.
  • Stores archived changes under openspec/changes/archive with metadata preserved.

Quick Start

Run openspec archive-change for a completed change to finalize it and move it to 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 changes in an openspec workflow?

The archive-change process finalizes and preserves implementation records for completed changes. It enforces artifact completion status checks before moving the records into the openspec/changes/archive directory.

What happens if openspec artifacts are not marked as complete before archiving?

The archival process enforces artifact completion status checks before allowing a change to be archived. This ensures that only fully finalized and verified changes are moved to the archive directory.

Can I sync delta-specs before archiving a change with openspec?

Yes, the archival operation performs a delta-spec sync assessment and prompts the user for optional synchronization. This ensures delta-specs are aligned before the change is moved to the archive.

Where are finalized changes stored after running openspec archive-change?

Archived changes are stored under the openspec/changes/archive directory. The process preserves all associated metadata while moving the finalized implementation records into this dedicated archive location.

Do I need the openspec CLI to finalize and archive change management records?

Yes, the openspec CLI is required to perform the archival operations, status checks, and delta-spec sync assessments. The process interacts with the user through the CLI to finalize implementation records.