openspec-archive-change

Archive completed OpenSpec changes by moving directories to the archive folder.

4|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/jaxxstorm/landlord --skill openspec-archive-change-jaxxstorm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/jaxxstorm/landlord/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/jaxxstorm/landlord --skill openspec-archive-change-jaxxstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to archive completed changes in the experimental OpenSpec workflow, helping keep the active workspace clean while preserving a traceable history.

Core Features & Use Cases

  • Archive a completed change by moving the change directory into openspec/changes/archive with a date-prefixed name.
  • Verify completion via openspec status, and optionally assess delta specs against main specs for synchronization notes.
  • Preserve critical configuration (e.g., .openspec.yaml) during archiving and generate a concise activity summary.

Quick Start

Use the openspec-archive-change skill to archive a completed change after implementation.

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 the openspec workflow?

To archive completed changes in the openspec workflow, you move the change directory into openspec/changes/archive with a date-prefixed name while preserving the original content and .openspec.yaml configuration.

What does the openspec status check do before archiving a change?

The openspec status check verifies completion before archiving a change, ensuring the change is finalized and optionally assessing delta specs against main specs for synchronization notes.

Does archiving an openspec change preserve the original directory content?

Yes, archiving an openspec change preserves the original directory content, including the critical .openspec.yaml configuration file, and generates a concise activity summary of the archive operation.

Do I need the openspec CLI to move changes to the archive folder?

Yes, you need the openspec CLI to move changes to the archive folder, as the archive operation enforces its use to finalize changes and produce the activity summary.

What is a delta-spec synchronization note in openspec archiving?

A delta-spec synchronization note is an optional assessment generated during openspec archiving that compares delta specs against main specs to track synchronization status before moving the change directory.

Why keep an archive of completed openspec changes instead of deleting them?

Keeping an archive of completed openspec changes instead of deleting them helps keep the active workspace clean while preserving a traceable history of finalized changes and their original configurations.