skills.rest
ishibata91
ishibata91COMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes with delta-spec synchronization and validation.

Updated Feb 3, 2026
Search Tags:#workflow#archive#openspec#change-management#artifact-status#delta-specs
One-click install
npx skills add https://github.com/ishibata91/ai-translation-engine-2 --skill openspec-archive-change-ishibata91
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/ishibata91/ai-translation-engine-2/tree/main/.agent/skills/openspec-archive-change
Command: npx skills add https://github.com/ishibata91/ai-translation-engine-2 --skill openspec-archive-change-ishibata91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Core Features & Use Cases

  • Validates artifact completion and task status before archiving to ensure only finished changes are moved.
  • Supports delta-spec synchronization by comparing local delta specs with main specs and offering sync options.
  • Archives the change into a date-stamped folder under openspec/changes/archive, preserving important metadata and the .openspec.yaml.
  • Provides a clear post-archive summary detailing the change, schema, archive location, and sync status.

Quick Start

Provide the change name (or let the system prompt to select an active change) and initiate the archive workflow to move the change to the archive directory.

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 change in OpenSpec?▼

To archive a completed change in OpenSpec, the workflow validates artifact completion and task status, then moves the change into a date-stamped folder under openspec/changes/archive while preserving metadata.

What is the best way to finalize an experimental workflow change after implementation?▼

Finalizing an experimental workflow change involves validating that all tasks and artifacts are complete, optionally synchronizing delta specs, and archiving the change with its metadata to a dedicated archive directory.

Do I need an OpenSpec environment to archive changes?▼

Yes, archiving changes requires an active OpenSpec environment initialized via npx openspec. The system relies on this environment to validate artifact completion and write to the openspec/changes/archive directory.

How does delta-spec synchronization work during change archiving?▼

Delta-spec synchronization compares local delta specs with main specs and offers sync options before archiving. This ensures the archived change accurately reflects the final state of the implemented features.

Can I archive an active change if some tasks are not yet complete?▼

No, the archive workflow validates artifact completion and task status before proceeding. Only fully finished changes are moved to the openspec/changes/archive directory to prevent archiving incomplete work.

What happens to the .openspec.yaml file when a change is archived?▼

When a change is archived, the system preserves important metadata including the .openspec.yaml file. The change is stored in a date-based folder within openspec/changes/archive, keeping all context intact.

Related Skills

Explore More Software Engineering Skills→
ybenitezfybenitezf

openspec-archive-change

Archive completed OpenSpec changes to a dated directory while preserving .openspec.yaml.

Community
Advanced
fjpulidopfjpulidop
9

opsx-archive

Archive completed openspec workflow changes with date-based names and summaries.

Community
Advanced
TranVanTienDatTranVanTienDat

openspec-archive-change

Archive completed changes with openspec CLI after completion checks.

Community
Intermediate
brainsnorkelbrainsnorkel

openspec-archive-change

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

Community
Advanced