openspec-archive-change

Archive completed OpenSpec changes with artifact and task checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dvazquezd/openspec-governance --skill openspec-archive-change-dvazquezd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/dvazquezd/openspec-governance/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/dvazquezd/openspec-governance --skill openspec-archive-change-dvazquezd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed changes within the OpenSpec governance framework, ensuring a clean and organized project history.

Core Features & Use Cases

  • Automated Archiving: Moves completed changes to a designated archive location.
  • Verification Checks: Ensures artifacts and tasks are complete before archiving, with options to proceed despite warnings.
  • Spec Synchronization: Facilitates syncing delta specs to main specs before archiving.
  • Use Case: After a feature development is finalized and verified, use this skill to formally close out the change and move it to the archive, updating main specifications as needed.

Quick Start

Use the openspec-archive-change skill to archive the change named 'user-profile-update'.

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 completed OpenSpec changes and move them out of my active project?

To archive completed OpenSpec changes, you can move the change directories to a designated archive location using date-based naming conventions, ensuring a clean and organized project history.

What checks are required before archiving a change in OpenSpec?

Before archiving a change in OpenSpec, verification checks are required to ensure that artifacts and tasks are complete. The process provides options to proceed despite warnings if needed.

Can I sync delta specifications to main specs when archiving an OpenSpec change?

Yes, you can optionally sync delta specifications to main specifications before archiving an OpenSpec change, ensuring your primary governance specs reflect the completed updates.

Do I need the OpenSpec CLI to archive a completed change?

Yes, you need the OpenSpec CLI and an active project context to operate the archive change process, as the workflow relies on the CLI to manage directory moves and spec synchronization.

What is the best way to formally close out a completed feature in a spec sync workflow?

The best way to close out a completed feature in a spec sync workflow is to archive the change after verifying task completion, which moves the change directory to an archive location.