openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: wwa-lab

Archive completed experimental workflow changes after verifying artifact and task completion.

Updated May 12, 2026

Search Tags:#software engineering #archiving #change management #software workflow #specification synchronization

Ready to run

npx skills add https://github.com/wwa-lab/legacy-spec-factory --skill openspec-archive-change-wwa-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/wwa-lab/legacy-spec-factory/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/wwa-lab/legacy-spec-factory --skill openspec-archive-change-wwa-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables the archiving of completed changes in the experimental workflow, providing a way to finalize and store changes once implementation is complete.

Core Features & Use Cases

Archive Changes: Permanently archive changes in the experimental workflow for safe storage.
Completion Check: Verify the completion status of artifacts and tasks before archiving.
Spec Sync: Offers options to sync delta specifications with the main specifications.
User Prompting: Prompts the user for input when necessary, such as selecting a change or confirming a step.

Quick Start

To archive a completed change, use the 'openspec archive-change' command and provide the change name if known.

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

To archive completed software changes, use the 'openspec archive-change' command and provide the change name. This verifies artifact and task completion before permanently storing the changes for safe finalization.

What does specification synchronization mean when finalizing change management?▼

Specification synchronization merges delta specifications generated during development with the main specifications. This optional step during change archiving ensures the primary software documentation reflects all finalized modifications.

Can I archive a software change before all implementation tasks are complete?▼

No, the archiving process checks the completion status of artifacts and tasks before proceeding. This completion verification ensures only fully finalized changes are permanently stored in the software workflow archive.

What is the best way to document and store finalized software workflow modifications?▼

The best way to document and store finalized modifications is through automated change archiving. This process permanently stores the changes and offers to sync delta specifications with your main software documentation.