openspec-archive-change

Archive completed OpenSpec changes to dated folders after validating artifacts and tasks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mohdakil2426/Device-Masker --skill openspec-archive-change-mohdakil2426
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/mohdakil2426/Device-Masker/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/mohdakil2426/Device-Masker --skill openspec-archive-change-mohdakil2426

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes to ensure reproducible workflows and clean project state by safely moving changes to an archive with proper metadata.

Core Features & Use Cases

  • Interactive change selection and archiving
  • Artifact and task completion validation before archiving
  • Delta-spec synchronization assessment with optional syncing
  • Date-based archive naming and preservation of configuration files

Quick Start

Choose a completed change and run the archive action to move it to the archive directory and preserve configuration artifacts.

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 automatically?

Archive completed OpenSpec changes automatically by validating artifacts and tasks, then moving the change to a dated archive folder. This workflow ensures a clean project state while preserving configuration files.

What is the best way to manage OpenSpec change archiving and delta spec synchronization?

Managing OpenSpec change archiving involves assessing delta specs and optionally syncing them before moving files. This ensures artifact status is correct and configuration files are preserved during the archive process.

How does OpenSpec artifact validation work before archiving a change?

OpenSpec artifact validation checks that all tasks and artifacts are completed before archiving a change. This prevents moving incomplete work to the dated archive folder and ensures reproducible workflows.

Can I sync delta specs when archiving completed OpenSpec changes?

You can optionally sync delta specs when archiving completed OpenSpec changes. The archiving process assesses delta spec presence and status, prompting you to synchronize specifications before moving the change.

Why does OpenSpec archive changes to a dated folder path?

OpenSpec archives changes to a dated folder path to ensure reproducible workflows and maintain a clean project state. This date-based naming organizes completed changes chronologically while preserving configuration files.

What happens to configuration files when OpenSpec changes are archived?

Configuration files are preserved when OpenSpec changes are archived. The archiving process includes guardrails that protect these files while moving completed changes and reporting a summary of the operation.