openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts, tasks, and delta specs.

Updated May 23, 2026
One-click install
npx skills add https://github.com/devturco/thiago-dev-template --skill openspec-archive-change-devturco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/devturco/thiago-dev-template/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/devturco/thiago-dev-template --skill openspec-archive-change-devturco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of finalizing and cleaning up an implemented change in an OpenSpec experimental workflow so the work is properly archived instead of lingering as “active.”

Core Features & Use Cases

  • Change selection with validation: Prompts you to choose a specific change when the name is not provided and avoids guessing.
  • Completion checks before archiving: Verifies artifact completion via openspec status --change "<name>" --json and warns about incomplete artifacts.
  • Task awareness and optional confirmation: Reads the tasks file (typically tasks.md) to detect incomplete tasks and asks for confirmation before proceeding.
  • Delta-spec sync assessment: Detects delta specs under openspec/changes/<name>/specs/, compares them to main specs in openspec/specs/<capability>/spec.md, and summarizes what would change before you decide.
  • Safe archiving procedure: Moves openspec/changes/<name> into openspec/changes/archive/YYYY-MM-DD-<name>/ after the checks and any optional sync step.

Quick Start

Run openspec-archive-change with the change name you want to finalize, and confirm prompts if any artifacts or tasks are incomplete.

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 from the active workflow?▼

Before archiving an OpenSpec change, the CLI checks artifact completion via openspec status and reads tasks.md to detect incomplete tasks. It warns you about incomplete items and prompts for confirmation before proceeding with the archiving workflow.

What is the best way to sync delta specs before archiving an OpenSpec change?▼

Yes, OpenSpec change archiving supports optional delta spec syncing. It detects delta specs under openspec/changes and uses an agent-driven openspec-sync-specs invocation to compare and sync them with main specs before moving the change to the archive folder.

How does OpenSpec prevent archiving the wrong change during workflow finalization?▼

OpenSpec prevents archiving the wrong change by prompting you to choose a specific change when the name is not provided, avoiding guessing. This ensures accurate change selection before verifying artifacts and tasks.

What happens to the filesystem when an OpenSpec change is archived?▼

When an OpenSpec change is archived, the filesystem moves the openspec/changes directory into openspec/changes/archive/YYYY-MM-DD-format. This safe archiving procedure occurs after completion checks and any optional delta spec syncing.