skills.rest
unbound-force
unbound-forceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes with validation and provenance.

3|11|Updated Feb 21, 2026
Search Tags:#automation#git#workflow#archive#openspec#change-management#delta-spec
One-click install
npx skills add https://github.com/unbound-force/unbound-force --skill openspec-archive-change-unbound-force
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/unbound-force/unbound-force/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/unbound-force/unbound-force --skill openspec-archive-change-unbound-force

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives completed OpenSpec changes to keep the workspace clean and auditable while preserving history.

Core Features & Use Cases

  • Validates artifact and task completion before archiving.
  • Performs optional delta-spec synchronization and archive-safe moves.
  • Preserves provenance by archiving under openspec/changes/archive with a date-stamped folder.

Quick Start

Provide the change name to archive, or let the tool prompt you to select from active changes.

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 after implementation?▼

Archiving OpenSpec changes involves pre-archive validation of tasks and artifacts, optional delta-spec synchronization, and executing safe git operations to move changes into openspec/changes/archive with proper provenance for a reliable repository state.

What is delta-spec synchronization in OpenSpec change management?▼

Delta-spec synchronization is an optional pre-archive step that aligns delta specifications before moving completed changes into the archive, ensuring the openspec/changes directory remains clean and auditable while preserving history.

How does the OpenSpec archival workflow validate tasks and artifacts?▼

The archival workflow enforces pre-archive validation by checking the completion status of all artifacts and tasks within the openspec/changes directory before permitting the change to be moved into the archive.

Does the OpenSpec archive process use safe git operations?▼

Yes, the OpenSpec archive process enforces safe git operations alongside pre-archive validation and delta-spec assessment to ensure a reliable, repeatable workflow when moving completed changes under openspec/changes/archive.

When should I archive completed changes in my git workflow?▼

You should archive completed changes after implementation to maintain a clean workspace, using pre-archive validation and provenance tracking to ensure only fully finished tasks and artifacts are moved to the dated archive folder.

Can I select which active change to archive in OpenSpec?▼

Yes, you can provide the specific change name to archive, or let the tool prompt you to select from the active changes currently residing in your openspec/changes directory.

Related Skills

Explore More Software Engineering Skills→
epamepam
503

openspec-archive-change

Validate and archive completed Openspec workflow changes while preserving configuration files.

Official
Advanced
jaxxstormjaxxstorm
4

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes into date-stamped directories.

Community
Advanced
AGiorgettiAGiorgetti

git-worktree-ops

Create, configure, and clean up isolated Git worktrees for parallel development.

Community
Advanced
PsychQuantPsychQuant
33

spectra-archive

Archive completed Spectrum changes to date-stamped openspec/changes/archive paths.

Official
Advanced