openspec-archive-change

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

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/ssttkkl/finance-tracker --skill openspec-archive-change-ssttkkl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/ssttkkl/finance-tracker/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/ssttkkl/finance-tracker --skill openspec-archive-change-ssttkkl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several error-prone manual checks: confirming artifacts are done, verifying tasks are complete, syncing delta specs into main specs, and moving the change directory into a dated archive. This Skill automates that entire finalization sequence with the openspec CLI. ## Core Features & Use Cases - Change Selection & Validation: Resolves the target change from user input or conversation context, checks artifact completion via openspec status --json, and counts incomplete tasks before archiving. - Delta Spec Sync Assessment: Compares delta specs against main specs, prompts to sync, runs the sync workflow inline, and verifies every capability matches before proceeding. - Safe Archive Execution: Creates the archive directory, generates a YYYY-MM-DD- prefixed target name without double-dating, detects name collisions, and moves the change directory. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the Skill warns about 2 incomplete tasks, syncs the delta specs into the main specs, and moves the change to changes/archive/2025-01-15-my-change/. ## Quick Start Archive the completed change named add-user-auth and sync its delta specs into the main specs before moving it.

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?

Run the archive workflow with the change name, or let it be inferred from context. The Skill checks artifact and task completion, assesses delta spec sync state, then moves the change directory into a dated folder under the changes archive directory.

How to sync delta specs into main specs before archiving?

When delta specs exist, the Skill compares each delta spec with its main spec and prompts you to sync. Choosing sync runs the openspec-sync-specs workflow inline, then re-verifies every capability before the archive proceeds.

Does archiving require the openspec CLI?

Yes, the workflow depends on the openspec CLI for status, instructions, and list commands. The optional archive-instructions lookup degrades gracefully on older CLI versions, but core commands must be available.

What happens if tasks are incomplete when archiving a change?

Incomplete tasks do not block archiving. The Skill counts unchecked tasks in the tasks file, displays a warning with the count, and asks for confirmation before proceeding with the archive.

Why does archiving fail with a target already exists error?

The archive target name is the change name prefixed with the current date, and the move fails if that folder already exists in the archive directory. Rename the existing archive or use a different date to resolve the collision.