openspec-archive-change

Archive completed OpenSpec changes under a date-based directory.

25|4|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/rozx/Tsukuyomi --skill openspec-archive-change-rozx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/rozx/Tsukuyomi/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/rozx/Tsukuyomi --skill openspec-archive-change-rozx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow to preserve an auditable history and maintain a clean project state.

Core Features & Use Cases

  • Prompts for change selection when the change name is not provided, ensuring the user always reviews the target change.
  • Validates artifact completion and task status before archiving, surfacing any warnings without blocking the archive.
  • Assesses delta-spec synchronization against main specs and can perform an optional sync step prior to archiving.
  • Archives the entire change directory under openspec/changes/archive with a date-based name while preserving .openspec.yaml and other config files.
  • Provides a clear summary of the archiving result including location, synopsis, and any warnings.

Quick Start

Provide the change name to archive, or let the system prompt you to choose an active change before archiving.

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 OpenSpec to preserve history?

Archive completed OpenSpec changes by validating artifact and task status, optionally syncing delta specs, and moving the change directory to openspec/changes/archive with a date-based name to preserve an auditable record.

What happens if my OpenSpec change has incomplete tasks or missing artifacts before archiving?

Archiving OpenSpec changes validates artifact completion and task status, surfacing any warnings without blocking the archive operation to ensure you are aware of incomplete items before finalizing.

Can I sync delta specs with main specs during the OpenSpec change archiving process?

Yes, the OpenSpec archive workflow assesses delta-spec synchronization against main specs and can perform an optional sync step prior to moving the change directory to the archive folder.

How are archived OpenSpec changes named and organized in the directory structure?

Archived OpenSpec changes are moved under openspec/changes/archive with a date-based naming convention while preserving .openspec.yaml and other config files for clean project state and auditable history.

Do I need to manually specify the change name when archiving an OpenSpec change?

No, if the change name is not provided, the OpenSpec archive workflow prompts you to select an active change, ensuring you always review and confirm the target change before archiving.

What is the best way to finalize an experimental workflow change in OpenSpec?

Finalize experimental OpenSpec changes by using a guided archive workflow that validates completion, optionally syncs delta specs, and archives the directory with a summary including location, synopsis, and warnings.