openspec-archive-change

Archive completed openspec experimental changes after validating artifact status and task completion.

6|Updated May 25, 2026
One-click install
npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill openspec-archive-change-zhentingwu-wzt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/zhentingWu-wzt/wgenty-code/tree/main/.wgenty-code/skills/openspec-archive-change
Command: npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill openspec-archive-change-zhentingwu-wzt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of managing the lifecycle of experimental changes by providing a structured, safe, and verifiable way to archive completed work within the openspec workflow.

Core Features & Use Cases

  • Artifact Verification: Automatically checks the completion status of all artifacts and tasks before archiving to prevent premature closure.
  • Delta Spec Synchronization: Assesses and synchronizes delta specifications with main specs to ensure documentation consistency.
  • Safe Archival: Moves completed changes to a dedicated archive directory with date-stamped naming, ensuring a clean workspace while preserving project history.

Quick Start

Use the openspec-archive-change skill to finalize and archive the current experimental change after verifying all tasks are complete.

Frequently Asked Questions about openspec-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely archive experimental changes after task completion?

To safely archive experimental changes, you can validate artifact status and task completion, then move the change directories to a date-stamped archive location. This ensures a clean workspace while preserving project history.

What is the best way to synchronize delta specifications with main documentation?

Synchronizing delta specifications with main documentation involves assessing completed changes and optionally merging the delta specs into the main specs. This maintains documentation consistency before final archival.

Do I need the openspec CLI to manage change archival?

Yes, you need the openspec CLI to manage change archival because it performs the required status checks and file system operations safely. Without it, verifying artifact completion and moving directories securely is not supported.

Why does my workflow prevent premature closure of experimental changes?

Your workflow prevents premature closure by automatically verifying the completion status of all artifacts and tasks before archiving. This validation step ensures incomplete work is not accidentally finalized.

Can I finalize experimental changes without moving them to a dedicated archive directory?

Finalizing experimental changes without moving them to a dedicated archive directory is not recommended. Safe archival requires relocating completed work with date-stamped naming to preserve project history and maintain a clean workspace.