skills.rest
thistleknot
thistleknotCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta specs.

Updated Apr 20, 2026
Search Tags:#archiving#openspec#artifact validation#spec synchronization#cli automation#workflow finalization#tasks checklist
One-click install
npx skills add https://github.com/thistleknot/skills --skill openspec-archive-change-thistleknot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/thistleknot/skills/tree/main/openspec-archive-change
Command: npx skills add https://github.com/thistleknot/skills --skill openspec-archive-change-thistleknot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec.

What problem does it solve?

It finalizes and archives a completed change in the experimental OpenSpec workflow while checking artifacts, tasks, and spec deltas so the archive reflects the actual completion state.

Core Features & Use Cases

  • Completion gating with user confirmation: Verifies artifact status via openspec status --json and checks tasks.md for incomplete tasks, prompting the user before proceeding when anything is unfinished.
  • Delta-spec synchronization assessment: Detects delta specs under openspec/changes/<name>/specs/ and compares them against the corresponding main specs under openspec/specs/<capability>/spec.md, then summarizes adds/modifications/removals/renames before prompting.
  • Archival with consistent naming and preservation: Moves openspec/changes/<name> into openspec/changes/archive/YYYY-MM-DD-<name>/ and preserves workflow metadata like .openspec.yaml during the move.
  • Use Case: After implementing a workflow change, archive it and optionally sync spec deltas to main specs while ensuring the change is truly complete (or explicitly acknowledged by the user).

Quick Start

Ask an AI to archive the currently finished OpenSpec change named "my-change" and, if delta specs exist, sync them to the main specs before archiving.

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 validating task completion?▼

To archive completed OpenSpec changes, the workflow checks artifact status via openspec status --json and verifies tasks.md for incomplete items. It prompts for confirmation if anything is unfinished before moving the change directory into a date-stamped archive location.

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

Delta specs under openspec/changes/<name>/specs/ are compared against main specs in openspec/specs/<capability>/spec.md. The system summarizes additions, modifications, removals, and renames, then prompts you to optionally sync these deltas to main specs before archiving.

Can I archive an OpenSpec change if some tasks in tasks.md are not finished?▼

Yes, you can archive an OpenSpec change with incomplete tasks. The system detects unfinished items in tasks.md and prompts you to explicitly acknowledge the incomplete state before proceeding with the archival.

Do I need the openspec CLI installed to archive changes in my repository?▼

Yes, the openspec CLI is required. The archival process depends on openspec CLI commands for listing available changes and inspecting completion status through openspec status --json before moving directories into the archive.

How are archived OpenSpec changes named and where are they stored?▼

Archived OpenSpec changes are moved into openspec/changes/archive/YYYY-MM-DD-<name>/ directories. This date-stamped naming ensures consistent organization while preserving workflow metadata files like .openspec.yaml during the move.

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

The best way to finalize an experimental OpenSpec workflow is to run artifact validation, check task completion in tasks.md, assess delta-spec synchronization against main specs, and then move the change into a date-stamped archive with metadata preserved.

Related Skills

Explore More Product & Management Skills→
wtg42wtg42

openspec-bulk-archive-change

Archive multiple openspec changes and resolve delta capability spec conflicts.

Community
Advanced
hongquandevhongquandev

openspec-sync-specs

Merge delta specs into main OpenSpec specification files.

Community
Advanced
gokhantaskangokhantaskan

openspec-archive-change

Archives completed experimental workflow changes after validating tasks and spec sync status with openspec CLI.

Community
Intermediate
remiverdiesenremiverdiesen
6

openspec-archive-change

Archive completed Openspec changes after validating artifacts and reviewing tasks.

Community
Advanced