openspec-archive-change

Archives a completed change after verifying tasks, artifacts, and delta spec sync.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/hi-yuki-922/accounting-assistant --skill openspec-archive-change-hi-yuki-922
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/hi-yuki-922/accounting-assistant/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/hi-yuki-922/accounting-assistant --skill openspec-archive-change-hi-yuki-922

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates 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 an archive directory with timestamped naming.
  • Status Verification: Checks artifact and task completion before archiving.
  • Delta Spec Sync: Assesses and optionally syncs delta specifications with main specs.
  • Use Case: After implementing a new feature and testing all its associated artifacts and tasks, use this Skill to formally archive the change, making it discoverable but out of the active development scope.

Quick Start

Use the openspec-archive-change skill to archive the change named 'user-authentication-flow'.

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, use this Skill to verify artifact and task completion, assess delta spec synchronization, and move the change directory to an archive location with a timestamped name after user confirmation.

What is the best way to verify task completion before archiving a change?

The best way to verify task completion is using the openspec CLI for status checks and listing. This Skill automates that verification, ensuring artifacts and tasks are complete before moving the directory to the archive.

Does archiving a change synchronize delta specs with the main specs?

Archiving a change assesses delta spec synchronization and optionally syncs delta specifications with the main specs, ensuring your archived changes reflect the fully updated project specifications before the directory is moved.

Do I need the openspec CLI to archive completed changes?

Yes, you need the openspec CLI to archive completed changes. The Skill requires the CLI specifically for performing status checks and listing artifacts to verify that all tasks and artifacts are fully completed.

Can I automate moving completed change directories to an archive location?

You can automate moving completed change directories by using this Skill, which handles the automatic transfer to an archive location with a timestamped name, keeping your active development scope clean and organized.

Why does the archiving process prompt for user confirmation?

The archiving process prompts for user confirmation to prevent premature archiving. It ensures the user explicitly approves the status verification and delta spec synchronization before the change directory is permanently moved to the timestamped archive.