openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: ssd-mkdocs-platform

Archive completed OpenSpec changes under openspec/changes/archive with metadata.

1|Updated Feb 7, 2026

Search Tags:#automation #workflow #archive #openspec #audit-trail #change-management

Ready to run

npx skills add https://github.com/ssd-mkdocs-platform/teams-board --skill openspec-archive-change-ssd-mkdocs-platform

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/ssd-mkdocs-platform/teams-board/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/ssd-mkdocs-platform/teams-board --skill openspec-archive-change-ssd-mkdocs-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed OpenSpec change to preserve history and prevent drift between active work and archived records.

Core Features & Use Cases

Guided archiving: creates a dated archive path under openspec/changes/archive and moves the change, preserving metadata and any .openspec.yaml, with optional delta-spec sync and artifact/task checks.
Guardrails: prompts for missing inputs, checks completion statuses, and informs about warnings without blocking the archive.

Quick Start

Archive the completed OpenSpec change by using the archive command and providing the change name when prompted.

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 OpenSpec changes to prevent drift?▼

OpenSpec archiving moves a completed change directory to a dated path under openspec/changes/archive. This preserves metadata and prevents drift between active work and archived records.

What happens if artifact and task checks are not fully completed before archiving?▼

The archiving workflow evaluates artifact and task completion statuses and informs you about any warnings. These guardrails do not block the archive process, allowing you to proceed while noting incomplete items.

When do I need to archive an OpenSpec change?▼

You need to archive an OpenSpec change when finalizing experimental workflow changes. This safely preserves the history and metadata of the completed work without interfering with ongoing active development.

Can I synchronize delta specs during the OpenSpec archiving process?▼

Yes, the OpenSpec archiving workflow includes optional delta-spec synchronization. It assesses delta spec differences and syncs them before moving the change directory to the archive.

How does the OpenSpec archive command handle missing change names?▼

The archive command applies guardrails by prompting you for the change name if it is not provided. This guided selection ensures the correct change directory is moved to the archive.