skills.rest
IchenDEV
IchenDEVCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed changes with openspec CLI after verifying artifacts and tasks.

Updated Apr 30, 2026
Search Tags:#workflow#specification#archive#change management#openspec
One-click install
npx skills add https://github.com/IchenDEV/f5 --skill openspec-archive-change-ichendev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/IchenDEV/f5/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/IchenDEV/f5 --skill openspec-archive-change-ichendev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill allows users to archive completed changes in the experimental workflow, ensuring that changes are finalized and documented after implementation is complete.

Core Features & Use Cases

  • Change Archiving: Finalize and archive completed changes for long-term storage and documentation.
  • Status Checking: Verify that all artifacts and tasks are complete before archiving.
  • Spec Syncing: Optionally sync delta specs with the main specs before archiving.
  • User Interaction: Provides prompts for user input to ensure changes are correctly archived and documented.

Quick Start

Archive the completed change by specifying the change name or selecting from available changes.

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

To archive completed changes, you select the change by name or from available options, and the workflow verifies all artifacts and tasks are finalized before archiving. It also optionally syncs delta specs with main specs.

What happens if artifacts or tasks are not complete before archiving a change?▼

Before archiving a change, status checks are performed to verify that all artifacts and tasks are complete. This ensures changes are fully finalized and documented before moving to long-term storage.

Does change management archiving require the openspec CLI?▼

Yes, finalizing and archiving changes in this experimental workflow requires the openspec CLI. The dependency is necessary to perform checks on task completion and sync delta specs.

Can I sync delta specs with main specs during the change archiving process?▼

Yes, you can optionally sync delta specs with main specs during archiving. The workflow prompts for user input to ensure changes are correctly finalized, documented, and synced before storage.

What is the best way to finalize and document experimental workflow changes?▼

The best way to finalize changes is using a dedicated archiving process that checks artifact completion, optionally syncs delta specs, and prompts for user input to ensure proper documentation for long-term storage.

Related Skills

Explore More Software Engineering Skills→
DanielShuguangDanielShuguang

openspec-archive-change

Archive completed experimental changes and synchronize incremental specifications with main specifications.

Community
Advanced
statick88statick88
1

sdd-archive

Merge delta specifications into main specs and archive completed change folders.

Community
Advanced
ywh0606ywh0606

opsx-verify

Verify OpenSpec changes for completion and readiness before archiving.

Community
Intermediate
darblexdarblex

git-essentials

Provide essential Git commands for version control, branching, and collaboration.

Community
Intermediate