openspec-archive-change

Validate artifacts and tasks, then archive completed changes to a dated folder.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow after implementation, ensuring artifacts and tasks are validated before archiving.

Core Features & Use Cases

  • Prompt change selection when needed to identify the correct change to archive.
  • Validate artifact completion and task status before archiving to ensure integrity.
  • Assess delta-spec synchronization and archive to openspec/changes/archive with a date-prefixed folder.

Quick Start

Provide the change name to archive, or allow me to prompt you to choose an active change, and I will validate artifacts, assess delta specs, and archive the change.

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 while ensuring artifacts and tasks are validated?

To archive completed changes safely, you validate artifact completion and task status, assess delta-spec synchronization, and move the change to a date-prefixed archive folder for an auditable record.

What happens if delta-specs are not synchronized before archiving a change?

Before archiving a change, delta-spec synchronization is assessed to ensure spec integrity. This validation step prevents incomplete or desynchronized specifications from being finalized into the dated archive.

How does the change archival process handle selecting which change to archive?

The change archival process prompts you to select an active change when a specific change name is not provided, ensuring the correct workflow artifacts are identified before validation and archival.

When do I need to archive changes to a date-prefixed folder in an openspec workflow?

You need to archive changes to a date-prefixed folder when an auditable record is required after implementation, ensuring completed tasks and synchronized delta-specs are safely finalized in openspec/changes/archive.

Can I use this archival workflow for changes with incomplete tasks or pending artifacts?

This archival workflow applies to cases where artifacts and tasks are complete. It validates artifact completion and task status before archiving to ensure integrity, preventing premature archival of incomplete work.

What is the best way to maintain an auditable archive of completed change management artifacts?

The best way to maintain an auditable archive is to finalize validated changes by moving them to a date-prefixed folder within openspec/changes/archive after confirming artifact completion and delta-spec synchronization.