skills.rest
EchoNoReturn
EchoNoReturnCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archives a completed change after verifying artifacts and tasks are finished.

Updated Mar 25, 2026
Search Tags:#workflow#archive#archiving#openspec#change-management#artifact-status#delta-specs
One-click install
npx skills add https://github.com/EchoNoReturn/task-manager --skill openspec-archive-change-echonoreturn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/EchoNoReturn/task-manager/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/EchoNoReturn/task-manager --skill openspec-archive-change-echonoreturn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives a completed change in the experimental workflow, preserving its state and moving it to a dedicated archive area after ensuring artifacts and tasks are finished.

Core Features & Use Cases

  • Prompts for the change name when not provided, ensuring you select an active, non-archived change.
  • Verifies artifact completion and task completion, surfacing any gaps and requesting confirmation before archiving.
  • Compares delta specs with main specs, provides a summary, and optionally syncs before archiving.
  • Safely archives the change into openspec/changes/archive/YYYY-MM-DD-<name> with the original metadata preserved.

Quick Start

Provide a change name or let the tool prompt you, then run the archive workflow to move the change into the 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 archive a completed change in an experimental workflow?▼

Archiving a completed change involves verifying all artifacts and tasks are finished, optionally syncing delta specs with main specs, and moving the change to openspec/changes/archive/YYYY-MM-DD-<name> while preserving original metadata.

What happens if artifacts or tasks are not finished when archiving a change?▼

When artifacts or tasks are unfinished, the archive workflow surfaces the specific gaps and requests your confirmation before proceeding, ensuring you do not archive incomplete changes accidentally.

How do delta specs compare to main specs before archiving?▼

The archiving process compares delta specs with main specs, provides a summary of differences, and optionally syncs the delta specs before safely archiving the completed change into the designated directory.

Can I archive an experimental change without specifying the change name?▼

Yes, when a change name is not provided, the tool prompts you to select an active, non-archived change, ensuring you choose a valid experimental change before verifying completion status and archiving.

When should I lock in the artifact state of a completed change?▼

You should lock in the artifact state after a change has been fully implemented and all associated tasks are finished, ensuring the final state is preserved safely in the archive directory before starting new experiments.

Related Skills

Explore More Software Engineering Skills→
TranVanTienDatTranVanTienDat

openspec-archive-change

Archive completed changes with openspec CLI after completion checks.

Community
Intermediate
Alex1980AlexAlex1980Alex

openspec-archive-change

Archive completed OpenSpec changes into dated directories after completion checks.

Community
Advanced
ConductionNLConductionNL

openspec-archive-change

Validate artifacts and tasks before archiving completed OpenSpec changes.

Official
Advanced
MiDouTechMiDouTech

openspec-archive-change

Archive completed openspec changes into date-prefixed directories after verification.

Official
Advanced