openspec-archive-change

Archive completed OpenSpec changes to timestamped directories with artifact and task checks.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/foxytanuki/bob --skill openspec-archive-change-foxytanuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/foxytanuki/bob/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/foxytanuki/bob --skill openspec-archive-change-foxytanuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the OpenSpec workflow by moving them to a timestamped archive, ensuring artifacts, tasks, and delta specs are considered during archival.

Core Features & Use Cases

  • Prompt-driven change selection when a change name is not provided.
  • Validate artifact and task completion before archiving.
  • Assess delta specs against main specs and optionally synchronize before archiving.
  • Move the change to openspec/changes/archive/YYYY-MM-DD-<name> while preserving metadata.
  • Generate a concise summary of the archival outcome.

Quick Start

Run the archive flow for a completed change and follow prompts to select the change name, verify artifacts and tasks, perform any necessary delta-spec synchronization, and finalize the archive.

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 changes in an OpenSpec workflow?

Archiving completed changes involves moving them to a timestamped directory named openspec/changes/archive/YYYY-MM-DD-<name> while preserving metadata and generating a concise summary of the archival outcome.

What is a delta-spec comparison and when is it needed during change archival?

Delta-spec comparison assesses change specifications against main specs before archiving. It is needed when finalizing a completed OpenSpec change to optionally synchronize specifications before the archival relocation.

Do I need to verify artifact and task completion before archiving a change?

Yes, the archival process validates artifact and task completion before moving the change. This ensures all required components and tasks are finished before relocating the change to the timestamped archive.

What happens if I don't provide a change name when archiving?

If a change name is not provided, the archival process enforces prompt-driven change selection. This prompts you to select the specific completed change you want to archive from available options.

Can I synchronize main specs with delta specs before moving a change to the archive?

Yes, you can optionally synchronize main specs with delta specs before archiving. The process assesses delta specs against main specs and performs optional synchronization before relocating the completed change.

Does the archive process preserve metadata when relocating completed changes?

Yes, the archive process preserves metadata when relocating completed changes. It moves the change to openspec/changes/archive/YYYY-MM-DD-<name> while retaining all associated metadata and generating a concise summary.