openspec-archive-change

Archive completed OpenSpec changes with delta-spec synchronization and summary reporting.

6|1|Updated Jun 1, 2025
One-click install
npx skills add https://github.com/rezics/rezics --skill openspec-archive-change-rezics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/rezics/rezics/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/rezics/rezics --skill openspec-archive-change-rezics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed OpenSpec change and ensure proper artifact and task completion, delta-spec synchronization, and safe archival.

Core Features & Use Cases

  • Interactive change selection: prompts to pick a valid OpenSpec change if none is provided.
  • Status validation: checks artifact completion and tasks, warning but not blocking archival.
  • Delta-spec synchronization: analyzes pending delta specs against main specs and optionally runs a sync.
  • Safe archiving & reporting: moves the change into openspec/changes/archive/YYYY-MM-DD-<name> while preserving configuration and provides a summary.

Quick Start

Prompt for a change name if needed, then run the archive workflow and follow the prompts to complete the process.

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 a completed OpenSpec change safely?

Archiving a completed OpenSpec change involves selecting the change, checking artifact completion and tasks, analyzing pending delta specs against main specs, and moving the change into openspec/changes/archive/YYYY-MM-DD-<name> while preserving configuration.

What happens to delta specs when I finalize an OpenSpec change?

When finalizing an OpenSpec change, the workflow analyzes pending delta specs against main specs and optionally runs a synchronization to ensure consistency before moving the change to the archive directory.

Can I archive an OpenSpec change if artifact tasks are not fully completed?

Yes, you can archive an OpenSpec change with incomplete tasks because the workflow checks artifact completion and tasks, issuing warnings but not blocking the archival process from completing.

Does the OpenSpec archive workflow preserve configuration files?

Yes, the OpenSpec archive workflow preserves configuration by moving the completed change into openspec/changes/archive/YYYY-MM-DD-<name> while maintaining all existing configuration settings.

What is the best way to manage completed changes in an OpenSpec workflow?

The best way to manage completed changes is using an archive workflow that validates artifacts, syncs delta specs, and moves changes to a dated archive directory while preserving configuration and generating a summary report.