skills.rest
echowaves
echowavesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed experimental workflow changes after validating artifacts and tasks.

Updated Feb 12, 2021
Search Tags:#archive#workflow management#openspec#artifact validation#spec sync#delta specs#task checklist
One-click install
npx skills add https://github.com/echowaves/WiSaw.cdk --skill openspec-archive-change-echowaves
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/echowaves/WiSaw.cdk/tree/main/.roo/skills/openspec-archive-change
Command: npx skills add https://github.com/echowaves/WiSaw.cdk --skill openspec-archive-change-echowaves

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you finalize and archive a completed change in an experimental workflow without losing context, while ensuring related artifacts, tasks, and optional delta-spec synchronization are handled intentionally.

Core Features & Use Cases

  • Change selection and completion validation: Lists available active changes when no name is provided, then checks artifact status to surface incomplete work before archiving.
  • Task completion verification: Reads the tasks file (typically tasks.md) to warn about incomplete checklist items and confirm whether to proceed.
  • Optional delta-spec sync assessment: Detects delta specs, compares them against main specs, summarizes the resulting adds/modifications/removals/renames, and prompts whether to sync or archive without syncing.
  • Deterministic archival with collision protection: Moves the change directory into a dated archive location, failing if the target archive already exists, and preserves workflow state like .openspec.yaml.
  • Operator-friendly completion reporting: Produces a clear final summary including archive location, used schema, and any warnings.

Quick Start

Run openspec-archive-change to archive your finished experimental change after confirming artifact and task completion and, if applicable, deciding whether to sync delta specs.

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 spec changes safely without losing incomplete task context?▼

To archive completed spec changes safely, the workflow validates artifact completion and task checklists before moving the change directory to a dated archive location. It ensures incomplete tasks are surfaced and confirmed before finalizing the archival process.

What happens to delta specs when I finalize a workflow change?▼

When finalizing a workflow change, delta specs are analyzed against main specs to summarize additions, modifications, removals, and renames. You are prompted to either sync these delta specs with the main specs or archive without syncing.

How does task checklist verification work before moving a change directory to the archive?▼

Task checklist verification reads the tasks file, typically tasks.md, to identify and warn about incomplete checklist items. It prompts the user to confirm whether to proceed with archiving despite the unfinished tasks.

Does the openspec archive process prevent overwriting existing archived changes?▼

Yes, the openspec archive process prevents overwriting by applying deterministic collision protection. It moves the change directory into a dated archive location and fails the operation if the target archive directory already exists.

Can I archive an experimental workflow change if the artifact status is not fully complete?▼

You can archive an experimental workflow change with incomplete artifacts, but the system will surface the incomplete status and warn you. It requires explicit user confirmation to proceed with archiving the unfinished work.

What is the best way to sync delta specs with main specs during change archival?▼

The best way to sync delta specs during change archival is to let the workflow analyze delta specs in openspec/changes against openspec/specs, summarize the modifications, and prompt you to confirm synchronization before moving the directory.

Related Skills

Explore More Software Engineering Skills→
SiddharthChillaleSiddharthChillale

openspec-continue-change

Create the next OpenSpec change artifact using the openspec CLI.

Community
Intermediate
joannanowakowskajoannanowakowska

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and task completion.

Community
Advanced
emergent-companyemergent-company
1

openspec-sync-specs

Synchronize delta specification files into main specification files using the openspec CLI.

Official
Advanced
brainsnorkelbrainsnorkel

openspec-archive-change

Archive completed changes in the experimental workflow via the openspec CLI.

Community
Advanced