skills.rest
B4san
B4sanCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed workflow changes after verifying artifact and task completion.

Updated Feb 19, 2026
Search Tags:#workflow#version control#specification#archive#change management#acfm
One-click install
npx skills add https://github.com/B4san/Calix-Pass --skill openspec-archive-change-b4san
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/B4san/Calix-Pass/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/B4san/Calix-Pass --skill openspec-archive-change-b4san

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed changes within an experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

  • Automated Archiving: Moves completed changes to a designated archive directory.
  • Status Verification: Checks artifact and task completion before archiving.
  • Spec Synchronization: Optionally syncs delta specifications with main specifications.
  • Use Case: After implementing a new feature defined by a workflow change, use this Skill to archive the completed change, update specifications, and maintain project order.

Quick Start

Use the openspec-archive-change skill to archive the change named 'feature-x'.

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 a completed workflow change and update specifications?▼

To archive a completed workflow change, use this Skill to verify artifact and task completion, optionally synchronize delta specifications with main specifications, and move the change directory to a designated archive location.

What is the process for synchronizing delta specifications before archiving a change?▼

Synchronizing delta specifications involves optionally syncing the delta specs with main specifications during the archiving process, ensuring project history stays organized and main specifications reflect completed changes.

Do I need the acfm CLI to verify spec status and archive changes?▼

Yes, you need the acfm CLI installed, as the archive change process requires it to execute spec status checks and listing operations before moving the change directory.

When should I archive an experimental workflow change?▼

You should archive an experimental workflow change after implementing a new feature, ensuring the associated artifacts and tasks are fully completed and verified before moving the directory.

What happens if artifacts or tasks are not completed before archiving?▼

The archiving process performs status verification to check artifact and task completion; if these are not complete, the change cannot be successfully archived until all requirements are met.

Related Skills

Explore More Software Engineering Skills→
B4sanB4san

acfm-spec-workflow

Initialize and manage AC Framework spec workflows using the acfm CLI.

Community
Intermediate
mazenyassergithubmazenyassergithub
6

git-master

Enforce atomic Git commits and manage history rewriting.

Community
Advanced
nextbysamnextbysam

spec-archiving

Archive completed change proposals and merge specification deltas into living documentation.

Community
Advanced
B4sanB4san

openspec-sync-specs

Merge delta specification changes into main specification documents.

Community
Advanced