skills.rest
GQAdonis
GQAdonisCOMMUNITY
Explore all skills by this author →
Website𝕏@gqadonisctoGitHub

openspec-archive-change

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

Updated Feb 16, 2026
Search Tags:#workflow#cli#archive#change management#spec-driven development#openspec#specs
One-click install
npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-archive-change-gqadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/GQAdonis/artifact-refiner-skill/tree/main/.kimi-code/skills/openspec-archive-change
Command: npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-archive-change-gqadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow requires checking artifact completion, task status, and delta spec synchronization before moving files, and doing this manually is error-prone and easy to get wrong. ## Core Features & Use Cases - Guided Change Selection: Resolves the target change from user input, conversation context, or an interactive prompt listing active changes. - 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, optionally runs an inline sync workflow, and verifies the result before archiving. - Use Case: After finishing implementation of a user-auth change, invoke the skill to confirm all artifacts are done, sync the delta specs into the main specs, and move the change into the dated archive directory. ## Quick Start Ask the assistant to archive the completed OpenSpec change named add-user-auth and confirm any warnings about incomplete tasks.

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 skill with a change name or let it infer one from context. It checks artifact and task completion, assesses delta spec sync state, then moves the change directory into an archive folder prefixed with the current date.

How does OpenSpec archiving handle unsynced delta specs?▼

The skill compares each delta spec against its main spec and prompts you to sync first or archive without syncing. If you choose sync, it runs the sync workflow inline and verifies all capabilities match before archiving.

Can I archive an OpenSpec change with incomplete tasks?▼

Yes, archiving is not blocked by incomplete tasks or artifacts. The skill displays a warning with the count of incomplete items and asks for confirmation before proceeding.

Does openspec-archive-change work with named stores?▼

Yes, it supports registered OpenSpec stores. It runs openspec store list to discover store ids and passes the --store flag on all commands that read or write specs and changes.

What happens if the archive target directory already exists?▼

The archive fails with an error suggesting you rename the existing archive or use a different date. The change directory is never overwritten or partially moved.

Related Skills

Explore More Software Engineering Skills→
carlosapgomescarlosapgomes

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
sanfordzhangsanfordzhang
1

openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict-aware delta-spec handling.

Community
Advanced
QuafadasQuafadas
13

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta specs.

Community
Advanced
ESO-ToolkitESO-Toolkit
2

rebase

Automate rebasing stacked Git branches after a squash merge.

Official
Advanced