skills.rest
ai-for-war
ai-for-warOFFICIAL
Explore all skills by this author →
GitHub

openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion.

1|Updated Mar 4, 2026
Search Tags:#workflow#cli#archive#change management#spec-driven development#OpenSpec#delta specs
One-click install
npx skills add https://github.com/ai-for-war/war_mind_fe --skill openspec-archive-change-ai-for-war
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/ai-for-war/war_mind_fe/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/ai-for-war/war_mind_fe --skill openspec-archive-change-ai-for-war

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, which is error-prone when done manually. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md before archiving. - Delta Spec Sync Assessment: Compares delta specs against main specs and optionally triggers a sync before archiving. - Safe Archiving: Moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name> with collision detection. - Use Case: After finishing implementation of a feature change, run this Skill to confirm all artifacts and tasks are done, sync spec deltas, and archive the change with a dated folder name. ## 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?▼

Run the archive workflow with a change name, or let it list active changes via `openspec list --json` for selection. It verifies artifacts and tasks, assesses delta spec sync state, then moves the directory to `openspec/changes/archive/YYYY-MM-DD-<name>`.

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

The workflow counts incomplete tasks marked `- [ ]` 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 first compares delta specs against main specs and shows a summary of pending changes. You choose whether to sync now, archive without syncing, or cancel, and archiving proceeds regardless of the sync choice.

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

The archive target uses the format `YYYY-MM-DD-<change-name>`, so archiving the same change twice on one day collides. Rename the existing archive or wait for a different date to resolve the conflict.

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

It requires the openspec CLI installed and a project initialized with the openspec directory structure. The change must exist under `openspec/changes/` and is selected interactively if no name is provided.

Related Skills

Explore More Software Engineering Skills→
CoderCoco-StudiosCoderCoco-Studios
1

openspec-propose

Generates complete OpenSpec change proposals with specs, design, and tasks artifacts.

Official
Advanced
amauryconstantamauryconstant
6

osx-generate-changelog

Generate a CHANGELOG.md from archived OpenSpec changes using Keep a Changelog format.

Community
Intermediate
cynkracynkra
1

openspec-sync-specs

Merge delta OpenSpec requirement blocks into main spec files per capability.

Official
Intermediate
JanuaryLabsJanuaryLabs
4

openspec-archive-change

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

Official
Advanced