openspec-archive-change

Archive completed OpenSpec change directories after validating readiness and preserving workflow context.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Kisthanny/MagnetFinder --skill openspec-archive-change-kisthanny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Kisthanny/MagnetFinder/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/Kisthanny/MagnetFinder --skill openspec-archive-change-kisthanny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely archive a completed OpenSpec change without losing required artifacts, status context, or synchronization history.

Core Features & Use Cases

  • Change Selection: Prompts you to choose the correct active change when the name is missing or ambiguous.
  • Completion Checks: Verifies artifact status, task completion, and workspace-planning limitations before any archive action.
  • Spec Synchronization: Reviews incremental spec deltas and supports syncing them to the main specification before archiving.
  • Archive Execution: Moves the finished change into a dated archive path and reports the result clearly.
  • Use Case: Use this Skill when a feature implementation is done and you need to close out the related OpenSpec change in a controlled way.

Quick Start

Ask the assistant to archive the completed OpenSpec change you want to close and let it verify readiness before moving anything.

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 OpenSpec change safely?

To archive a completed OpenSpec change safely, the workflow validates artifact status, checks task completion, optionally syncs spec deltas, and moves the directory to a dated archive path.

What does it mean to sync spec deltas before archiving a change?

Syncing spec deltas means reviewing incremental specification changes and merging them into the main specification before the change directory is archived, ensuring no context is lost.

How do I know if my OpenSpec change is ready to be archived?

Readiness is determined by verifying artifact status via OpenSpec CLI commands and inspecting tasks to ensure completion, while also checking for any workspace-planning limitations.

Can I archive an OpenSpec change if the name is missing or ambiguous?

Yes, if the change name is missing or ambiguous, the workflow prompts you to select the correct active change directory before proceeding with any validation or archive actions.

What happens to incomplete OpenSpec changes during the archive process?

Incomplete changes trigger safeguards that halt the archive process, preventing filesystem move operations when artifact status checks or task reviews reveal the change is not fully ready.