skills.rest
remiverdiesen
remiverdiesenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed Openspec changes after validating artifacts and reviewing tasks.

6|Updated Nov 21, 2025
Search Tags:#workflow#cli#archive#change management#openspec#spec sync
One-click install
npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-archive-change-remiverdiesen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/remiverdiesen/ark-fork/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-archive-change-remiverdiesen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finalizes a completed Openspec change by checking readiness, handling warnings, and archiving the change safely.

Core Features & Use Cases

  • Validates artifact status with openspec status before archiving.
  • Reviews task completion and warns about unfinished work.
  • Assesses delta specs, optionally syncs them, and moves the change into an archive directory.
  • Use it when a change implementation is finished and needs to be preserved for audit or handoff.

Quick Start

Use the openspec-archive-change skill to archive the completed change named my-change after confirming any warnings.

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

To archive a completed Openspec change safely, use this skill to validate artifact status, review open tasks, optionally sync delta specs, and move the change directory into the archive path after handling confirmation warnings.

What happens to unsynced delta specs during Openspec change archiving?▼

During Openspec change archiving, unsynced delta specs are assessed and optionally synchronized before the change directory is moved into the archive, ensuring spec consistency for audit or handoff.

Does archiving an Openspec change require the openspec CLI?▼

Yes, archiving an Openspec change requires openspec CLI access to validate artifact status, check readiness, and execute the directory move into the validated archive path.

How do I handle incomplete artifacts or open tasks before archiving an Openspec change?▼

Before archiving an Openspec change, the skill reviews task completion and warns about unfinished work or incomplete artifacts, prompting confirmation handling to proceed with the finalization workflow safely.

When should I use an Openspec change archiving workflow?▼

You should use an Openspec change archiving workflow when a change implementation is finished and needs to be preserved for audit or handoff, requiring artifact checks and optional spec synchronization.

Related Skills

Explore More Software Engineering Skills→
kuchida1981kuchida1981

openspec-archive-change

Archive completed openspec changes into the dated archive tree.

Community
Advanced
rock-hurock-hu

openspec-archive-change

Archive completed openspec changes into dated paths after validating artifacts and tasks.

Community
Advanced
CatsofsufferingCatsofsuffering
5

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with status checks.

Community
Advanced
DataCoveyDataCovey
27

openspec-archive-change

Archive a completed OpenSpec change to preserve artifacts and align with the experimental workflow.

Official
Advanced