openspec-archive-change

Archives completed OpenSpec changes with delta sync and artifact validation.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/woutervanranst/Arius7 --skill openspec-archive-change-woutervanranst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/woutervanranst/Arius7/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/woutervanranst/Arius7 --skill openspec-archive-change-woutervanranst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental OpenSpec workflow, enabling safe finalization and archival after implementation.

Core Features & Use Cases

  • Orchestrates end-to-end archival: prompts for change selection when missing, validates artifact completion and task status, assesses delta specs against main specs, optionally syncs, and moves the change into a dated archive path while preserving metadata.
  • Ensures metadata integrity by retaining configuration files (e.g., .openspec.yaml) during archiving and providing a clear summary of outcomes.

Quick Start

Run the archive workflow to finalize and move the change to the archive, validating artifacts and tasks, assessing delta specs, and preserving metadata.

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 change in the OpenSpec workflow?

To archive a completed OpenSpec change, run the archive workflow to validate artifact completion, check task status, assess delta specs against main specs, and move the change into a dated archive path while preserving metadata.

What does OpenSpec change archival validate before finalizing?

OpenSpec change archival validates artifact completion and task status via openspec status, analyzes delta specs against main specs, optionally syncs them, and preserves configuration files like .openspec.yaml during the move.

When do I need to archive an OpenSpec change?

You need to archive an OpenSpec change after implementation is complete and you want to safely finalize it, ensuring all artifacts and tasks are validated and delta specs are synchronized with main specs.

Can I archive an OpenSpec change without selecting it first?

Yes, the archival workflow enforces change selection when it is missing by prompting you to choose which completed change to finalize and move into the archive directory.

Where does the OpenSpec archive workflow move completed changes?

The OpenSpec archive workflow moves completed changes to openspec/changes/archive/YYYY-MM-DD-<name>, applying a date-stamped archival path while retaining metadata and configuration files.

What happens to delta specs during OpenSpec change archival?

During OpenSpec change archival, delta specs are analyzed against main specs and optionally synchronized, ensuring the archived change reflects the latest spec state before being moved.