openspec-archive-change

Archive completed openspec workflow changes into dated directories after validating completion.

Updated May 5, 2026
One-click install
npx skills add https://github.com/agoodway/goodday --skill openspec-archive-change-agoodway
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/agoodway/goodday/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/agoodway/goodday --skill openspec-archive-change-agoodway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you safely finalize an implemented change in an experimental workflow by verifying that its artifacts and tasks are complete, optionally syncing any delta specs to the main specs, and then archiving the change without losing workflow metadata.

Core Features & Use Cases

  • Change finalization with guardrails: Prompts for change selection when not provided, and warns/asks confirmation when artifacts or tasks are incomplete.
  • Completion validation: Uses openspec status --change ... --json to ensure artifacts are marked done, and checks a tasks file for unchecked tasks.
  • Delta spec sync assessment: Detects delta specs under openspec/changes/<name>/specs/, summarizes adds/changes/removals/renames vs main specs, and prompts whether to sync before archiving.
  • Archiving with deterministic naming: Moves openspec/changes/<name>/ into openspec/changes/archive/YYYY-MM-DD-<name>/ and prevents overwriting existing targets.

Quick Start

Ask the AI to archive the completed change named "feature-x" after checking artifacts, tasks, and delta-spec differences against the main 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 a completed openspec change safely without losing metadata?▼

You can archive an openspec change by validating its artifacts and tasks via status checks, optionally syncing delta specs to main specs, and moving the directory into a dated archive folder while preserving .openspec.yaml metadata.

What happens if I try to archive an openspec change with incomplete tasks or artifacts?▼

When archiving an openspec change with incomplete tasks or artifacts, the process detects unchecked items using status checks and tasks file validation, then warns you and prompts for confirmation before proceeding with the finalization.

Do I need to sync delta specs to main specs before archiving an openspec change?▼

You do not strictly need to sync delta specs before archiving, but the workflow assesses differences under the changes directory, summarizes adds, changes, and removals, and prompts you to optionally invoke spec sync before moving the change folder.

How does openspec handle naming conflicts when archiving a change directory?▼

Openspec prevents overwriting existing targets during archiving by applying deterministic naming, moving the original change directory into a specifically dated archive folder formatted as YYYY-MM-DD followed by the change name.

Can I batch archive multiple completed openspec changes at once?▼

Archiving multiple completed openspec changes at once is not supported by this workflow, as it requires prompting the user for individual change selection and confirmations when incomplete artifacts or tasks are detected.