openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts, tasks, and spec synchronization.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-archive-change-ismaelsoilet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/ismaelsoilet/ismaelsoilet-landing/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-archive-change-ismaelsoilet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves multiple manual checks—artifact completion, task status, and delta spec synchronization—before safely moving the change into the archive. This Skill automates that entire finalization sequence so nothing is archived prematurely or left out of sync. ## Core Features & Use Cases - Guided Change Selection: Resolves the target change from context, auto-selects when only one is active, or prompts with a list of active changes when ambiguous. - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning before archiving with open items. - Delta Spec Sync Assessment: Compares delta specs against main specs, offers to sync via the openspec-sync-specs workflow, and verifies the merge before moving anything. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the Skill validates all artifacts, optionally syncs specs into the main spec tree, then moves the change into a date-prefixed archive directory. ## Quick Start Ask the assistant to archive the completed OpenSpec change, optionally naming the change to finalize.

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?▼

Invoke the archive workflow and optionally name the change. The Skill checks artifact and task completion, assesses delta spec sync state, then moves the change directory into a date-prefixed folder under the changes archive directory.

What happens if I archive a change with incomplete tasks?▼

The Skill counts incomplete tasks marked with `- [ ]` in the tasks file and displays a warning with the count. It asks for confirmation before proceeding, so archiving with open tasks is possible but never silent.

Does archiving sync delta specs to the main specs automatically?▼

Not automatically. The Skill compares each delta spec against its main spec and prompts you to sync now or archive without syncing. If you choose sync, it runs the openspec-sync-specs workflow inline and verifies the merge before archiving.

What CLI is required for the OpenSpec archive workflow?▼

The workflow requires the openspec CLI installed on the machine. Commands like `openspec status`, `openspec list`, and `openspec instructions` are executed with JSON output to drive selection, validation, and archiving.

Why does archiving fail with a target already exists error?▼

The archive target name is the change name prefixed with the current date in YYYY-MM-DD format. If a directory with that name already exists in the archive folder, the operation fails and suggests renaming the existing archive or using a different date.