openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: meettechnology

Archive completed openspec changes with artifact and task completion checks.

1|Updated Apr 13, 2026

Search Tags:#automation #workflow #artifacts #archive #openspec #change-management #spec-sync

Ready to run

npx skills add https://github.com/MeetTechnology/AutoHire --skill openspec-archive-change-meettechnology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/MeetTechnology/AutoHire/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/MeetTechnology/AutoHire --skill openspec-archive-change-meettechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed experimental changes to keep workspaces clean and preserve provenance, while ensuring all artifacts and tasks are finalized or properly flagged.

Core Features & Use Cases

Automates the archive process for completed openspec changes, including artifact and task status checks.
Supports delta-spec synchronization assessment and preserves metadata when moving changes to archive.
Provides a clear, timestamped archival path and a final summary of what was archived, what was synced, and what warnings (if any) occurred.

Quick Start

Provide the change name to archive and confirm any incomplete artifacts or tasks 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 while preserving artifacts and metadata?▼

To archive openspec changes, the workflow checks artifact and task completion, assesses delta-spec synchronization, and moves the change directory to openspec/changes/archive using a date-based name to preserve provenance and metadata.

What happens if I try to archive an openspec change with incomplete tasks or artifacts?▼

When archiving openspec changes with incomplete tasks or artifacts, the workflow enforces prompts to check their status, requiring you to confirm or properly flag them before proceeding to finalize the directory move.

Does archiving openspec changes require delta spec synchronization beforehand?▼

Archiving openspec changes assesses optional delta specs for synchronization before finalizing the move, ensuring that any required spec-sync operations are handled and properly logged in the final summary.

What is the best way to keep workspaces clean after finalizing experimental change management workflows?▼

The best way to keep workspaces clean is to archive completed experimental openspec changes, which moves the change directory to a timestamped archival path and outputs a final summary of synced items and warnings.

Why does the openspec archive process use a date-based naming convention for moved change directories?▼

The openspec archive process uses a date-based naming convention when moving change directories to ensure clear chronological provenance, prevent naming collisions, and maintain an organized historical record of finalized artifacts.

Can I automate the archival of openspec changes without manually checking task completion?▼

Automating openspec change archival includes built-in checks for artifact and task completion, prompting for confirmation on incomplete items to ensure safe finalization without requiring manual pre-checks.