openspec-archive-change

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

4|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jin1c-3/obsidian-advanced-maps --skill openspec-archive-change-jin1c-3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Jin1c-3/obsidian-advanced-maps/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/Jin1c-3/obsidian-advanced-maps --skill openspec-archive-change-jin1c-3

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 an archive with a dated name. This Skill automates that entire finalization sequence through the openspec CLI. ## Core Features & Use Cases - Completion verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md before archiving, warning but not blocking on gaps. - Delta spec sync assessment: Compares delta specs against main specs, summarizes pending adds, modifications, removals, and renames, and optionally runs an inline sync with post-sync verification before archiving. - Dated archival: Moves the change directory into an archive folder with a YYYY-MM-DD- prefixed name, preserving .openspec.yaml and refusing to overwrite existing archives. - Use Case: After finishing implementation of a user-auth change, ask the agent to archive it; the Skill verifies all artifacts and tasks, syncs the delta specs into the main specs, and moves the change to changes/archive/2025-01-15-user-auth/. ## Quick Start Archive the completed change named add-login-flow 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 change in OpenSpec?

Invoke 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 changes/archive with a YYYY-MM-DD prefix.

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 never blocked but you are informed of the gaps.

Does the archive workflow sync delta specs into main specs?

Yes, when delta specs exist it compares them against main specs and prompts to sync. The sync runs inline with post-sync verification of every affected capability, and archiving stops if the main specs do not match.

Can I archive a change stored in a registered OpenSpec store?

Yes, run openspec store list --json to discover registered store ids, then pass --store <id> on commands that read or write specs and changes. The flag stays sticky for the rest of the workflow.

What happens if the archive target directory already exists?

The archive fails with an error rather than overwriting. You are advised to rename the existing archive or use a different date, and the change directory is left untouched.