skills.rest
Alex1980Alex
Alex1980AlexCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes into dated directories after completion checks.

Updated Mar 29, 2026
Search Tags:#workflow#cli#archive#openspec#specs#task-tracking
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill openspec-archive-change-alex1980alex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill openspec-archive-change-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you finalize an implementation by moving a completed OpenSpec change into archive after checking readiness, avoiding premature archival and preserving workflow history.

Core Features & Use Cases

  • Change selection: Lists active changes and lets the user choose when the target name is not obvious.
  • Completion checks: Reviews artifact status and task progress before archiving.
  • Safe archival: Detects delta specs, offers sync options, prevents archive name collisions, and preserves repository metadata.
  • Use case: Use it when a feature branch is done and you want to close out the corresponding OpenSpec change cleanly.

Quick Start

Ask the Skill to archive the completed OpenSpec change named feature-x and confirm whether you want to sync any delta specs first.

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 after finishing a feature branch?▼

To archive a completed OpenSpec change, select the active change, verify artifact and task completion, optionally sync delta specs, then move it into a dated archive directory while preserving repository metadata.

When should I archive OpenSpec specs and what checks are needed first?▼

Archive OpenSpec specs when implementation is finished and artifact status plus task progress are verified, ensuring no premature archival occurs and workflow history is preserved in the archive directory.

Do I need the OpenSpec CLI to archive finished workflow changes?▼

Yes, the OpenSpec CLI is required to access the workflow commands needed to list active changes, check completion status, and safely move finished specs into the archive.

What happens to delta specs when archiving an OpenSpec change?▼

When delta specs are detected during OpenSpec archival, the workflow offers options to sync them before moving the change, ensuring spec updates are not lost during the finalization process.

How does OpenSpec prevent archive name collisions when finalizing changes?▼

OpenSpec archival prevents archive name collisions by checking the dated archive directory before moving the completed change, while also preserving the .openspec.yaml file and saving a memory summary of the archived change.

Related Skills

Explore More Software Engineering Skills→
kevinxo328kevinxo328
5

openspec-archive-change

Archive completed openspec workflow changes after validating artifacts and task status.

Community
Advanced
ssd-mkdocs-platformssd-mkdocs-platform
1

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with metadata.

Official
Advanced
harqianharqian
1

openspec-archive-change

Archive completed changes in the experimental workflow with openspec CLI.

Community
Intermediate
KisthannyKisthanny
1

openspec-archive-change

Archive completed OpenSpec change directories after validating readiness and preserving workflow context.

Community
Advanced