openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta specs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you finalize and archive an OpenSpec experimental change safely by validating that artifacts, tasks, and spec deltas are in a consistent state before moving the change into the archive.

Core Features & Use Cases

  • Change selection with no guessing: Prompts the user to choose an active change if a change name is not provided.
  • Completion validation before archive: Checks artifact completion via openspec status and task completion via a tasks.md-style checklist.
  • Delta spec sync assessment: Detects delta specs, summarizes what would be synced to main specs, and prompts the user to sync or archive without syncing.
  • Guardrail-based prompting: Prompts before proceeding when artifacts or tasks are incomplete, and shows a clear summary at the end.
  • Safe archive move with conflict protection: Moves the change directory into an archive folder using a date-based target name and fails if the target already exists.

Use case: You finish implementing a change in the experimental workflow and want to archive it, but you need confidence that its artifacts are complete and that any spec deltas are either synced or explicitly skipped.

Quick Start

Ask it to archive your completed experimental change named "my-change" after verifying artifacts, tasks, and delta specs as needed.

Frequently Asked Questions about openspec-archive-change

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

FAQPage Schema
How do I safely archive a completed OpenSpec change and validate artifacts?

To archive a completed OpenSpec change, you validate artifact and task completion, assess delta spec synchronization, and move the change directory into the archive with a date-stamped name. This prevents guessing and ensures safe workflow finalization.

What happens to delta specs when finalizing an OpenSpec workflow?

When finalizing an OpenSpec workflow, the system detects delta specs, summarizes what would be synced to main specs, and prompts you to either sync the delta specs or archive the change without syncing them.

Can I move an OpenSpec change to the archive if task checklist validation fails?

You can move an OpenSpec change to the archive with incomplete tasks, but guardrail-based prompting will warn you before proceeding. It checks task completion via a tasks.md-style checklist to ensure you explicitly confirm the finalization.

How does the OpenSpec archive process handle naming conflicts in the archive folder?

The OpenSpec archive process handles naming conflicts by using a date-based target name for the moved directory. It fails safely if the target directory already exists, providing conflict protection during the finalization move.

Do I need to specify the change name to start the OpenSpec archive process?

You do not need to specify the change name to start the OpenSpec archive process. If a change name is not provided, the system prompts you to select an active change using openspec list and openspec status JSON data.