openspec-archive-change

Automate archiving completed changes via the openspec CLI with JSON status checks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/min-zou/obsidian-doc --skill openspec-archive-change-min-zou
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/min-zou/obsidian-doc/tree/main/format/areas/system/agent-skills/codex/openspec-archive-change
Command: npx skills add https://github.com/min-zou/obsidian-doc --skill openspec-archive-change-min-zou

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec CLI, and includes scripts (resource) components.

What problem does it solve?

This Skill assists users in archiving completed changes in the experimental workflow, allowing them to finalize and store changes after implementation.

Core Features & Use Cases

  • Archive Completion: Facilitates the archiving process for changes that are ready to be finalized.
  • Input Prompting: Dynamically prompts for a change name if not provided, ensuring user selection.
  • Status Checking: Validates the completion of artifacts and tasks, including delta spec synchronization.
  • Error Handling: Offers warnings for incomplete tasks and artifacts, providing a confirmation step.
  • Summary Display: Provides a detailed summary of the archive completion, including the schema used and whether specs were synced.

Quick Start

Archive a completed change by executing 'archive-change Skill --change <change-name>'.

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 using the openspec CLI?

To archive completed changes, execute the archive-change command with the openspec CLI and specify the change name. The workflow validates completion status, checks delta spec synchronization, and provides a summary of the archived artifacts.

What happens if artifact or task completion checks fail during change archiving?

If artifact or task completion checks fail during change archiving, the process issues warnings for incomplete items and prompts for user confirmation before proceeding. This ensures you explicitly approve finalizing changes with missing or incomplete artifacts.

Do I need to manually provide a change name when archiving in openspec?

You do not need to manually provide a change name when archiving in openspec if it is unspecified. The workflow dynamically prompts you to select the target change name before validating completion status and proceeding with archiving.

How does delta spec synchronization work during change management archiving?

Delta spec synchronization is handled as a critical part of the archiving workflow. The process parses JSON output from the openspec CLI to verify completion status, ensuring delta specs are synced before finalizing and storing the implemented changes.

Can I finalize and store experimental workflow changes if tasks are incomplete?

You can finalize and store experimental workflow changes with incomplete tasks, but the workflow provides error handling warnings and requires explicit user confirmation at critical steps before allowing the archive process to complete.

What summary details are displayed after archiving a completed change?

After archiving a completed change, the workflow displays a detailed summary including the schema used for archiving and whether the delta specifications were successfully synced during the finalization process.