openspec-archive-change

Archive completed openspec change directories after validating artifacts and tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects using experimental openspec changes need a reliable, auditable way to finalize work without accidentally losing progress or leaving incomplete artifacts and tasks. This Skill prevents accidental archiving by validating artifact and task completion, summarizing delta spec differences, and requiring explicit user confirmation before moving change directories to an archive location.

Core Features & Use Cases

  • Guided change selection: Prompts the user to choose an active change when a name isn't provided and prevents silent guesses.
  • Completion validation: Parses openspec status JSON and task files to surface incomplete artifacts and tasks and requests user confirmation if anything is outstanding.
  • Delta spec assessment and optional sync: Compares delta specs to main specs, summarizes adds/changes/removals, and offers to sync before archiving while preserving important metadata.
  • Safe archive operation: Creates a date-prefixed archive folder, checks for name collisions, moves the change directory while preserving .openspec.yaml, and reports a clear summary.

Quick Start

Ask the agent to archive the change named feature-x and confirm artifact completion, task completion, and optional spec sync before moving it to openspec/changes/archive.

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 completed openspec changes without losing progress?

To safely archive completed openspec changes, you can use a guided workflow that validates task and artifact completion, summarizes delta spec differences, and requires explicit user confirmation before moving the change directory to an archive location.

What is the best way to verify task completion before moving an openspec change to an archive?

The best way to verify task completion before archiving an openspec change is to parse openspec status JSON outputs and task files, which surfaces any incomplete artifacts or tasks and prompts for user confirmation if outstanding items are detected.

Can I sync delta specs to main specs right before archiving openspec changes?

Yes, you can sync delta specs before archiving openspec changes by comparing delta specs against openspec/specs, summarizing additions, changes, and removals, and optionally syncing them while preserving important metadata like .openspec.yaml.

Do I need openspec CLI JSON outputs to finalize and archive openspec changes?

Yes, you need openspec CLI JSON outputs from openspec list and openspec status commands to finalize and archive changes, as these outputs provide the required artifact status and task completion data for validation.

How does the archiving process handle name collisions in the openspec archive folder?

The archiving process handles name collisions by creating a date-prefixed archive folder and checking for existing names before moving the change directory, ensuring no existing archived changes are overwritten.