openspec-archive-change

Archive experimental openspec changes after verifying task and artifact completion.

2|Updated Aug 15, 2025

Search Tags:#version control #workflow management #openspec #change tracking #archive change

Ready to run

npx skills add https://github.com/rfhayn/forager --skill openspec-archive-change-rfhayn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/rfhayn/forager/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/rfhayn/forager --skill openspec-archive-change-rfhayn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

This Skill unit simplifies the process of finalizing and archiving experimental changes in the openspec workflow, providing a structured way to manage and organize changes post-implementation.

Core Features & Use Cases

Selective Change Archive: Users can archive specific changes to mark them as completed and finalize them within the workflow.
Change Completion Verification: It checks for the completion status of all associated artifacts and tasks before finalization.
Optional Delta Spec Sync: It allows optional syncing of delta specifications with the main specifications before archiving.

Quick Start

Run 'archive-change <change-name>' to archive the specified change after completing the implementation phase.

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 experimental changes in an openspec workflow?▼

To archive experimental changes in an openspec workflow, use the archive-change command followed by the change name. This finalizes completed implementations and marks them as done within the version control system.

Can I sync delta specifications before finalizing an openspec change?▼

Yes, you can optionally sync delta specifications with main specifications before archiving an openspec change. This ensures all modified specs are synchronized before the experimental change is marked as fully completed.

Does archiving an openspec change verify task and artifact completion?▼

Yes, archiving an openspec change includes completion verification. The process checks the completion status of all associated artifacts and tasks to ensure everything is finished before finalizing the workflow.

Do I need the openspec CLI tool to manage change tracking and archiving?▼

Yes, you need the openspec CLI tool to manage change tracking and archiving. The Skill requires this dependency to automate the archival of experimental changes within the openspec architecture.

What is the best way to finalize experimental changes in version control?▼

The best way to finalize experimental changes in version control is using a structured workflow management tool like openspec. It automates completion checks and archives changes to maintain a clean project history.

When should I not use automated archive change for workflow management?▼

You should not use automated archive change if your experimental changes are incomplete. The process checks for the completion of all associated tasks and artifacts, blocking finalization if required workflow elements are missing.