openspec-archive-change

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

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/hpelaez73/elprado-backend --skill openspec-archive-change-hpelaez73
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/hpelaez73/elprado-backend/tree/main/.trae/skills/openspec-archive-change
Command: npx skills add https://github.com/hpelaez73/elprado-backend --skill openspec-archive-change-hpelaez73

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. Doing this manually is error-prone and can leave main specs out of sync with the change. ## Core Features & Use Cases - Guided change selection: Infers the change from context, auto-selects when only one active change exists, or prompts with a list of active changes when ambiguous. - Completion verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning before archiving with open items. - Delta spec sync assessment: Compares delta specs against main specs, optionally runs the inline sync workflow, and verifies the result before archiving. - Safe archiving: Moves the change directory into a date-prefixed archive folder, failing safely if the target already exists. - 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 main specs, and moves the change to changes/archive/2024-05-01-user-auth/. ## Quick Start Ask the assistant to archive the completed OpenSpec change named my-feature, confirming any warnings about incomplete tasks or unsynced specs.

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 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 date-prefixed folder under the changes archive directory.

What happens if tasks are incomplete when archiving a change?

The skill counts incomplete tasks marked with `- [ ]` in the tasks file and displays a warning with the count. It asks for confirmation before proceeding, so archiving is never blocked but you are informed of open items.

Does archiving sync delta specs to the main specs?

Yes, if delta specs exist the skill compares them against main specs and offers to sync before archiving. The sync runs inline and is verified against every capability; if verification fails, the archive stops and nothing is moved.

Can I archive a change in a specific OpenSpec store?

Yes, when a store is named or the work lives in one, the skill discovers registered store ids with `openspec store list --json` 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 suggesting you rename the existing archive or use a different date. The change directory is not moved, so nothing is lost and you can retry after resolving the conflict.