skills.rest
wonderslife
wonderslifeCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes with date-based names and metadata.

13|3|Updated Apr 7, 2026
Search Tags:#automation#workflow#archive#openspec#change#delta-spec#artifact-status
One-click install
npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill openspec-archive-change-wonderslife
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/wonderslife/pdd-skills-v3/tree/main/skills/openspec/openspec-archive-change
Command: npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill openspec-archive-change-wonderslife

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed OpenSpec change after implementation to finalize and preserve the state of changes.

Core Features & Use Cases

  • End-to-end archival workflow: validates artifact and task completion, assesses delta specs, prompts for optional synchronization, and archives with a date-stamped path.
  • Delta spec synchronization: detects delta specs against main specs and optionally runs a sync before archiving, keeping the primary specs in sync.
  • Preserves provenance and metadata: retains .openspec.yaml during archival and produces a summary of the archive.
  • Prompts and guardrails: prompts the user for change selection when not provided and clearly reports any incomplete items.

Quick Start

Provide the change name to archive and let the tool perform the archival workflow.

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 after implementation?▼

To archive completed OpenSpec changes, the workflow validates artifact and task completion, optionally synchronizes delta specs, and moves the change to a date-stamped archive path to finalize and preserve state.

What happens to delta specs when archiving an OpenSpec change?▼

During OpenSpec change archiving, the tool detects delta specs against main specs and prompts for optional synchronization to keep primary specs updated before finalizing the archive.

Can I archive an OpenSpec change if artifacts or tasks are incomplete?▼

Archiving an OpenSpec change requires completed artifacts and tasks; the tool applies guardrails to validate completion status and clearly reports any incomplete items before proceeding.

How does OpenSpec preserve metadata when archiving changes?▼

OpenSpec preserves provenance during change archiving by retaining the .openspec.yaml file and moving the change to openspec/changes/archive with a date-based name, then producing a summary.

What is the best way to finalize an OpenSpec workflow after code implementation?▼

Finalizing an OpenSpec workflow involves archiving the completed change, which validates tasks, synchronizes delta specs with main specs, and stores the change state in a date-stamped archive directory.

Do I need to provide a change name to start the OpenSpec archiving process?▼

Providing a change name starts the OpenSpec archiving process directly; if omitted, the tool prompts you to select a specific change before applying validation and archival workflows.

Related Skills

Explore More Software Engineering Skills→
ondataondata
9

openspec-verify-change

Verify code changes against openspec delta specs and task artifacts.

Official
Advanced
jaxxstormjaxxstorm
4

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes into date-stamped directories.

Community
Advanced
arestivoarestivo

openspec-sync-specs

Merge delta specs into main OpenSpec specifications deterministically.

Community
Advanced
psaccpsacc

openspec-archive-change

Archive completed openspec changes after verifying artifacts, tasks, and delta specs.

Community
Advanced