skills.rest
ilaziness
ilazinessCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes after validating tasks and syncing delta specs.

6|1|Updated Dec 19, 2025
Search Tags:#workflow#artifacts#archiving#openspec#spec sync#delta specs#cli automation
One-click install
npx skills add https://github.com/ilaziness/vexo --skill openspec-archive-change-ilaziness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/ilaziness/vexo/tree/main/.crush/skills/openspec-archive-change
Command: npx skills add https://github.com/ilaziness/vexo --skill openspec-archive-change-ilaziness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec.

What problem does it solve?

This Skill helps you safely finalize an experimental OpenSpec change by verifying that its artifacts and related tasks are complete, optionally syncing delta specs back to the main specs, and then archiving the change directory with a traceable date-stamped name.

Core Features & Use Cases

  • Interactive change selection: If the change name is missing or ambiguous, it prompts you to choose from active changes using the available OpenSpec CLI output.
  • Completion validation with guardrails: It checks artifact completion via openspec status --json and reviews task completion by scanning the tasks file (e.g., tasks.md), warning you before proceeding when anything is incomplete.
  • Delta-spec synchronization assessment: If delta specs exist, it compares them against the corresponding main specs, summarizes the resulting adds/modifications/removals/renames, and prompts you to sync or archive without syncing.
  • Archiving with collision protection: It moves the change directory into openspec/changes/archive/ using YYYY-MM-DD-<change-name>, preventing overwrites by failing if the target already exists.
  • Clear completion reporting: It outputs a concise summary including schema used, archive location, and whether specs were synced or skipped.

Quick Start

Ask the Skill to archive your completed OpenSpec change named "auth-login-workflow" and sync any delta specs back to the main specs when needed.

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 spec changes and sync delta specs?▼

To archive completed OpenSpec spec changes, you validate artifact and task completion via `openspec status --json`, optionally sync delta specs to main specs, and move the change directory into a date-stamped archive location.

What does it mean to sync delta specs to main specs in OpenSpec?▼

Syncing delta specs to main specs in OpenSpec means comparing experimental change specifications against the corresponding main specifications, summarizing additions, modifications, removals, and renames, and applying those changes to finalize the configuration.

Do I need the OpenSpec CLI to finalize and archive spec changes?▼

Yes, you need the OpenSpec CLI installed to finalize and archive spec changes, as the workflow relies on `openspec status --json` output for listing active changes and validating artifact completion before archiving.

Can I archive an OpenSpec change directory if its tasks are incomplete?▼

You can attempt to archive an OpenSpec change with incomplete tasks, but the Skill scans task markdown files for completion signals and warns you before proceeding, acting as a guardrail against finalizing unfinished work.

What happens if a date-stamped archive folder already exists in OpenSpec?▼

If a date-stamped archive folder already exists in `openspec/changes/archive/`, the archiving process fails to prevent overwrites, ensuring collision protection for your finalized change directories.

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

The best way to finalize an experimental OpenSpec workflow is using an automated archiving process that validates completion status, syncs delta specs to main specs if needed, and moves the directory to a traceable date-stamped archive.

Related Skills

Explore More Software Engineering Skills→
jankneumannjankneumann
4

openspec-archive-change

Archive completed OpenSpec change directories to a dated location.

Community
Advanced
RyanCallahan312RyanCallahan312

openspec-archive-change

Archive completed OpenSpec changes to an auditable directory with metadata.

Community
Advanced
cynkracynkra
1

openspec-bulk-archive-change

Archive multiple active OpenSpec changes after validating task completion and resolving delta-spec conflicts.

Official
Advanced
belingudbelingud
30

openspec-archive-change

Archive completed OpenSpec changes with verified artifacts and delta specs.

Community
Advanced