openspec-archive-change

Archive completed workflow changes after verifying artifacts, tasks, and delta specs.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/zthxxx/hams --skill openspec-archive-change-zthxxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/zthxxx/hams/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/zthxxx/hams --skill openspec-archive-change-zthxxx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of archiving completed changes in workflow management systems, ensuring consistency and reducing manual effort.

Core Features & Use Cases

  • Change Selection and Verification: Prompts the user to select active changes, verifies artifact and task completion statuses, and assesses delta specification updates.
  • Safe Archiving Process: Moves change directories into timestamped archive folders, with conflict detection and prompting for sync if needed.
  • Use Case: A project manager completes a change and wishes to archive it after ensuring all artifacts and tasks are finalized, with an option to sync specifications beforehand for consistency.

Quick Start

Invoke this skill to automate archiving a completed change, automatically verifying statuses, syncing specs if necessary, and storing the change in an organized archive directory.

Frequently Asked Questions about openspec-archive-change

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

FAQPage Schema
How do I automate workflow change archiving with validation checks?

Workflow change archiving validates artifact completion, task statuses, and delta specification updates before moving change directories into timestamped archive folders. It prompts for specification synchronization if conflicts are detected, ensuring safe file moves.

What does delta spec comparison check during the change archiving process?

Delta spec comparison during change archiving assesses specification updates and detects conflicts between active workflow changes. If differences are found, it prompts for specification synchronization to ensure all dependencies are verified before final archiving.

Can I archive completed workflow changes without manually verifying task completion?

You can archive completed changes without manual verification. The archiving process automatically confirms artifact and task completion statuses, assesses delta specification updates, and ensures all dependencies are synchronized before moving change directories into timestamped archive folders.

How do I handle conflicts when moving change directories into archive folders?

Handle archiving conflicts through built-in conflict detection that prompts for specification synchronization. The safe archiving process moves change directories into timestamped archive folders, ensuring structured archiving and preventing file overwrites in workflow documentation scenarios.

What's the best way to ensure specifications are synchronized before final archiving?

The best way to ensure specifications are synchronized before final archiving is to use automated delta spec comparison with conflict detection. This verifies artifact and task completion statuses and prompts for specification sync, ensuring all dependencies are checked before storing changes in organized archive directories.