skills.rest
pvtvv
pvtvvCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

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

Updated Jul 10, 2026
Search Tags:#workflow#cli#archive#change management#spec-driven development#openspec#delta specs
One-click install
npx skills add https://github.com/pvtvv/climber-app --skill openspec-archive-change-pvtvv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/pvtvv/climber-app/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/pvtvv/climber-app --skill openspec-archive-change-pvtvv

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 and validation: Resolves the target change from user input or context, checks artifact completion via openspec status --json, and counts incomplete tasks in tasks.md. - Delta spec sync assessment: Compares delta specs against main specs, summarizes pending adds/modifications/removals/renames, and optionally runs an inline sync with verification before archiving. - Dated archival: Moves the change directory into an archive/ folder with a YYYY-MM-DD- prefix, preventing duplicate archive targets. - Use Case: After finishing implementation of a user-auth change, ask the assistant to archive it; the Skill verifies all artifacts and tasks, syncs the delta specs into the main specs, and moves the change into the archive with a summary report. ## Quick Start Ask the assistant 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 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 an archive folder with a YYYY-MM-DD prefix.

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

The Skill compares each delta spec against its main spec and shows a combined summary of adds, modifications, removals, and renames. Choosing sync runs the openspec-sync-specs workflow inline and re-verifies every capability before archiving proceeds.

Can I archive a change with incomplete tasks or artifacts?▼

Yes, archiving is not blocked by incomplete artifacts or tasks. The Skill displays a warning listing incomplete items and asks for confirmation before proceeding, then notes the warnings in the final summary.

Does the openspec archive workflow support multiple stores?▼

Yes, when a store is named or detected, the Skill runs openspec store list --json to discover registered store ids and passes --store <id> on all commands that read or write specs and changes for the rest of the workflow.

What happens if the archive target directory already exists?▼

The archive fails with an error rather than overwriting. The Skill suggests renaming the existing archive or using a different date, and never stacks a second date prefix on an already dated change name.

Related Skills

Explore More Software Engineering Skills→
ducthang-hubducthang-hub

openspec-propose-ai-kit

Generate proposal, design, and tasks artifacts using the openspec CLI.

Community
Intermediate
josemartinrodriguezmortalonijosemartinrodriguezmortaloni

sdd-archive

Sync delta specifications into main specs and archive change folders.

Community
Advanced
emergent-companyemergent-company
1

openspec-bulk-archive-change

Archive multiple completed changes with openspec CLI after validating status and resolving conflicts.

Official
Advanced
NUMU-IONUMU-IO
2

speckit-git-validate

Validates the current Git branch against feature naming conventions.

Official
Intermediate