openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and specification sync.

4|9|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/DataDave-Dev/weftmap --skill openspec-archive-change-datadave-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/DataDave-Dev/weftmap/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/DataDave-Dev/weftmap --skill openspec-archive-change-datadave-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides you through finalizing and archiving completed OpenSpec changes while checking artifact status, task completion, specification synchronization, and archive naming conflicts.

Core Features & Use Cases

  • Change Selection: Lists active changes and prompts you to select one when no change name is provided.
  • Completion Validation: Checks artifact and task status, identifies incomplete work, and requests confirmation before proceeding.
  • Specification Sync and Archiving: Assesses delta specifications, supports synchronization, preserves change metadata, and archives the completed change using a date-based destination.
  • Use Case: After implementing a feature managed with OpenSpec, use this Skill to verify the work, synchronize its specifications, and move the completed change into the archive.

Quick Start

Use the openspec archive change skill to finalize and archive the completed change named "your-change-name".

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 and verify task completion?

To archive completed OpenSpec changes, the skill validates artifact status, checks task completion, and moves the finalized change into a date-based archive directory. It prompts for confirmation if any incomplete work is detected before proceeding.

What happens to delta specifications when finalizing an OpenSpec workflow?

When finalizing an OpenSpec workflow, the skill assesses delta specifications and supports specification synchronization. It preserves change metadata during the archival process to maintain accurate historical records.

Do I need the OpenSpec CLI to archive changes in my repository?

Yes, you need the OpenSpec CLI installed to archive changes in your repository. The skill relies on the CLI to interact with registered stores, perform completion checks, and manage the archival workflow.

Can I archive an OpenSpec change if there is incomplete work or unresolved tasks?

You can archive an OpenSpec change with incomplete work, but the skill will identify the unresolved tasks and artifacts, then explicitly request your confirmation before proceeding with the archival.

How does OpenSpec handle archive path collisions when moving completed changes?

OpenSpec prevents archive path collisions by using date-based destination paths for completed changes. This ensures that each archived specification and its associated metadata are stored uniquely.