openspec-archive-change

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

1|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-archive-change-miftah-fentaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Miftah-Fentaw/GymPulse/tree/main/.qwen/skills/openspec-archive-change
Command: npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-archive-change-miftah-fentaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks—artifact completion, task status, and delta spec synchronization—before the change directory can be safely moved to 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: Infers the 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 and confirming before proceeding. - Delta spec sync assessment: Compares delta specs against main specs, optionally runs an inline sync workflow, and verifies the result before archiving. - Use Case: After finishing implementation of a user-auth change, ask the assistant to archive it; the Skill validates all artifacts, syncs spec deltas into the main specs, and moves the change into archive/2024-01-15-user-auth/ with a summary. ## Quick Start Ask the assistant to archive the completed change named add-user-auth using the openspec archive workflow.

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

Provide the change name or let the Skill infer it from context. It checks artifact and task completion, assesses delta spec sync state, then moves the change directory into an archive folder with a YYYY-MM-DD prefix.

What happens if tasks are incomplete when archiving a change?▼

The Skill counts incomplete tasks marked with `- [ ]` in tasks.md and displays a warning with the count. It asks for confirmation before proceeding, so archiving is never blocked but always informed.

Does archiving sync delta specs to the main specs?▼

Yes, if delta specs exist the Skill compares them against main specs and offers to sync before archiving. The sync runs inline and is verified across every capability before the change directory is moved.

Can I archive a change in a registered OpenSpec store?▼

Yes, run `openspec store list --json` to discover store ids, then the Skill passes `--store <id>` on all spec and change commands. The flag stays sticky for the rest of the workflow.

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

The archive target name is the change name with a YYYY-MM-DD prefix, and the move fails if that directory already exists in the archive. Rename the existing archive or use a different date to resolve it.