openspec-archive-change

Archive completed OpenSpec changes after validating completion and syncing delta specs.

18|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/igamenovoer/houmao --skill openspec-archive-change-igamenovoer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/igamenovoer/houmao/tree/main/tests/fixtures/plain-agent-def/skills/openspec-archive-change
Command: npx skills add https://github.com/igamenovoer/houmao --skill openspec-archive-change-igamenovoer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec.

What problem does it solve?

It helps you finalize an OpenSpec change by validating completion status, optionally syncing delta specs, and archiving the change into a dated location without losing important workflow files.

Core Features & Use Cases

  • Change selection & validation: Prompts you to choose an active change when the name isn’t provided and inspects completion status using OpenSpec CLI JSON outputs.
  • Quality checks before archiving: Warns about incomplete artifacts and incomplete tasks, then confirms before proceeding.
  • Delta spec sync assessment: Detects delta specs and generates a combined summary of required updates, letting you choose whether to sync before archiving.
  • Safe archive operation: Moves the change directory into openspec/changes/archive/YYYY-MM-DD-<change-name>/, failing if the target already exists and preserving files (including .openspec.yaml).

Quick Start

Archive your completed OpenSpec change named "Change42" for finalization and archival.

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 without losing workflow files?

To archive a completed OpenSpec change safely, the workflow validates artifact and task completion via CLI JSON outputs, optionally syncs delta specs, and moves the directory into a dated archive folder while preserving files like .openspec.yaml.

What happens if I try to archive an OpenSpec change with incomplete tasks or uncommitted artifacts?

Before archiving an OpenSpec change, the system inspects completion status using CLI JSON outputs and warns you about incomplete artifacts or tasks, requiring confirmation before proceeding with the filesystem move to prevent data loss.

Do I need to sync delta specs before finalizing an OpenSpec workflow?

Syncing delta specs before finalizing an OpenSpec workflow is optional; the process detects delta specs, generates a combined sync summary, and lets you choose whether to call openspec-sync-specs before moving the change to the archive.

Can I archive an OpenSpec change without specifying the change name in the CLI?

Yes, you can archive an OpenSpec change without specifying the name; the system prompts you to select an active change, validates its status, and safely moves it into openspec/changes/archive/YYYY-MM-DD-<change-name>/.

Why does archiving an OpenSpec change fail if the target directory already exists?

Archiving an OpenSpec change fails if the target dated directory already exists to prevent overwriting previous archive data, ensuring the guarded filesystem move into openspec/changes/archive remains a safe finalization operation.