skills.rest
phuchoang2603
phuchoang2603COMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

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

1|1|Updated Jan 25, 2026
Search Tags:#workflow#cli#archive#change management#spec-driven development#openspec#spec sync
One-click install
npx skills add https://github.com/phuchoang2603/nixos --skill openspec-archive-change-phuchoang2603
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/phuchoang2603/nixos/tree/main/home/base/cli/skills/openspec-archive-change
Command: npx skills add https://github.com/phuchoang2603/nixos --skill openspec-archive-change-phuchoang2603

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves checking artifact completion, task status, and delta spec synchronization before moving the change into an archive directory, and doing this manually is error-prone. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning before archiving unfinished work. - Delta Spec Sync Assessment: Compares delta specs against main specs, optionally runs an inline sync workflow, and verifies the merge before archiving. - Store-Aware Archiving: Supports registered OpenSpec stores via --store <id> flags and moves the change into a date-prefixed archive directory. - Use Case: After finishing implementation of a user-auth change, ask the agent to archive it; the skill verifies all artifacts and tasks, syncs spec deltas, and moves the change to archive/2024-01-15-user-auth. ## Quick Start Ask the agent 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 change in OpenSpec?▼

Invoke the archive workflow with a change name, or let it infer the change from context. The skill checks artifact and task completion, assesses delta spec sync state, then moves the change directory into a date-prefixed archive folder.

How to sync delta specs to main specs before archiving?▼

The skill compares each delta spec with its main spec and prompts you to sync. If you choose sync, it runs the openspec-sync-specs workflow inline, then re-verifies every capability before allowing the archive to proceed.

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 work with registered stores?▼

Yes, the skill supports standalone OpenSpec stores. It runs openspec store list --json to discover store ids and passes --store <id> 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 if the date-prefixed target name already exists in the archive directory. The skill suggests renaming the existing archive or using a different date instead of overwriting.

Related Skills

Explore More Software Engineering Skills→
carlosapgomescarlosapgomes

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
HankLiu447HankLiu447
3

superspec:archive

Apply delta changes to main specs and archive documents after verification.

Community
Intermediate
daodaoedudaodaoedu

openspec-bulk-archive-change

Archive multiple OpenSpec changes with conflict detection and spec syncing.

Official
Advanced
agoodwayagoodway
1

workie

Manage git worktree workflows with branch-isolated PostgreSQL databases for Phoenix/Elixir projects.

Official
Advanced