openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion.

3|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/mambo-wang/CodingHub --skill openspec-archive-change-mambo-wang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/mambo-wang/CodingHub/tree/main/.qoder/skills/openspec-archive-change
Command: npx skills add https://github.com/mambo-wang/CodingHub --skill openspec-archive-change-mambo-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves checking artifact status, verifying task completion, syncing delta specs, and moving directories safely. Doing this manually is error-prone and can leave specs out of sync or archives misnamed. ## Core Features & Use Cases - Completion Verification: Runs openspec status --json to check artifact completion and scans tasks.md for incomplete checklist items before archiving. - Delta Spec Sync Assessment: Compares delta specs against main specs and optionally triggers the openspec-sync-specs workflow before archiving. - Safe Archive Operation: Moves the change directory into a date-prefixed archive folder (YYYY-MM-DD-<name>) with collision detection and workspace-planning guardrails. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the skill prompts you to select the change, warns about incomplete tasks, syncs specs if needed, and archives 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 OpenSpec change?▼

Invoke the archive workflow with a change name, or let it prompt you with a list of active changes from `openspec list --json`. It verifies artifact and task completion, then moves the change directory into an archive folder named YYYY-MM-DD-<change-name>.

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

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

Does archiving sync delta specs to the main specs?▼

Yes, if delta specs exist the skill compares them against main specs under openspec/specs and shows a summary of additions, modifications, and removals. You can choose to sync via the openspec-sync-specs workflow or archive without syncing.

Can I archive a workspace-planning change?▼

No. When the status JSON reports actionContext.mode as workspace-planning, the skill stops and explains that workspace archive is not supported. It does not move workspace changes into repo-local archives or edit linked repositories.

What happens if an archive with the same date and name already exists?▼

The archive operation fails with an error rather than overwriting. The skill suggests renaming the existing archive or using a different date to resolve the collision.