skills.rest
nodesource
nodesourceOFFICIAL
Explore all skills by this author →
Website𝕏@NodeSourceGitHub

openspec-archive-change

Archives completed openspec changes after verifying artifact and task completion status.

6|7|Updated Jun 4, 2026
Search Tags:#cli#archive#task tracking#change management#openspec#spec workflow
One-click install
npx skills add https://github.com/nodesource/nsolid-plugin --skill openspec-archive-change-nodesource
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/nodesource/nsolid-plugin/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/nodesource/nsolid-plugin --skill openspec-archive-change-nodesource

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in the openspec workflow requires checking artifact status, task completion, and spec synchronization before moving files into an archive, which is error-prone when done manually. ## Core Features & Use Cases - Completion Verification: Runs openspec status --json to check artifact completion and reads tasks.md to count incomplete tasks before archiving. - Delta Spec Sync Assessment: Compares delta specs against main specs and offers to sync changes via the openspec-sync-specs skill before archiving. - Safe Archiving: 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 confirm any incomplete artifacts or tasks, optionally syncs specs, and produces a summary of the archived change. ## Quick Start Archive the completed openspec change named add-user-auth and sync its delta specs to the main specs first.

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 skill with a change name, or let it prompt you with available active changes via `openspec list --json`. It verifies artifacts and tasks, then moves the change directory into an archive folder named with the current date.

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

The skill 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 sync delta specs to the main 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.

Can I archive a workspace-planning change in openspec?▼

No. If the status JSON reports `actionContext.mode: "workspace-planning"`, the skill stops and explains that workspace archive is not supported, without moving workspace changes into repo-local archives.

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 not moved, preventing accidental overwrites.

Related Skills

Explore More Software Engineering Skills→
aehrcaehrc
133

openspec-continue-change

Create the next OpenSpec artifact in a predefined workflow using CLI checks.

Official
Advanced
Charles5277Charles5277
45

openspec-onboard

Guide developers through OpenSpec workflow phases from proposal to archival.

Community
Intermediate
echowavesechowaves

openspec-archive-change

Archive completed experimental workflow changes after validating artifacts and tasks.

Official
Intermediate
jankneumannjankneumann
4

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes while detecting spec conflicts.

Community
Advanced