skills.rest
zh-impact
zh-impactCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archives completed OpenSpec changes with artifact, task, and spec sync verification.

Updated Apr 7, 2026
Search Tags:#workflow#cli#archive#change management#spec-driven development#openspec#delta specs
One-click install
npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-archive-change-zh-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/zh-impact/agent-feeder/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-archive-change-zh-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks—verifying artifact completion, confirming tasks are done, syncing delta specs, and moving directories—which is error-prone when done by hand. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and scans tasks.md for incomplete items before archiving. - Delta Spec Sync Assessment: Compares delta specs against main specs and offers to sync changes before archiving. - Safe Archiving: Moves the change directory to openspec/changes/archive/ with a date-prefixed name, failing safely if the target already exists. - Use Case: After finishing implementation of a feature change, run this Skill to confirm all artifacts and tasks are complete, optionally sync specs, and archive the change with a clear summary. ## Quick Start Archive the completed change 'add-user-auth' and sync its delta specs to the main specs.

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 change in OpenSpec?▼

Invoke the archive workflow with a change name, or let it prompt you to select from active changes listed via openspec list --json. It verifies artifacts and tasks, then moves the change directory to openspec/changes/archive/ with a YYYY-MM-DD prefix.

What happens if tasks are incomplete when archiving an OpenSpec change?▼

The workflow counts incomplete tasks marked with '- [ ]' in tasks.md and displays a warning with the count. It asks for confirmation before proceeding, so archiving is not blocked but you are informed of unfinished work.

Does archiving an OpenSpec change sync delta specs automatically?▼

No, it assesses delta specs against main specs and shows a summary of pending changes first. You can choose to sync via the openspec-sync-specs skill, archive without syncing, or cancel.

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

The archive target uses the format YYYY-MM-DD-<change-name>, and the move fails if that directory already exists in openspec/changes/archive/. Rename the existing archive or archive on a different date to resolve it.

What are the requirements for using the OpenSpec archive workflow?▼

It requires the openspec CLI installed and a project structured with openspec/changes directories. The change should have artifacts tracked by openspec status and optionally a tasks.md file and delta specs.

Related Skills

Explore More Software Engineering Skills→
MiDouTechMiDouTech

openspec-archive-change

Archive completed openspec changes into date-prefixed directories after verification.

Official
Advanced
daodaoedudaodaoedu

openspec-bulk-archive-change

Archive multiple OpenSpec changes with conflict detection and spec syncing.

Official
Advanced
mazhewittmazhewitt

openspec-sync-specs

Merge delta specification changes into canonical main specs with idempotent updates.

Community
Advanced
JanuaryLabsJanuaryLabs
4

openspec-archive-change

Archive completed openspec changes after verifying artifacts and syncing delta specs.

Official
Advanced