skills.rest
huangjia2019
huangjia2019COMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes into dated directories with status checks.

114|47|Updated Apr 13, 2026
Search Tags:#workflow#archive#openspec#change-management#artifact-status#delta-specs
One-click install
npx skills add https://github.com/huangjia2019/sdd-in-action --skill openspec-archive-change-huangjia2019
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/huangjia2019/sdd-in-action/tree/main/week2/code/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/huangjia2019/sdd-in-action --skill openspec-archive-change-huangjia2019

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental OpenSpec workflow to keep history clean and prevent rework.

Core Features & Use Cases

  • Archive a completed change after implementation
  • Check artifact completion and task status
  • Prompt for delta-spec sync if needed and perform archiving
  • Preserve configuration and move the change into an archive directory named with the current date

Quick Start

Provide the change name (or select from active changes when prompted) and archive after optional delta-spec synchronization.

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 while preserving configuration?▼

To archive completed OpenSpec changes, this skill moves the change into a dated archive directory while preserving the .openspec.yaml file, preventing rework and keeping project history clean.

What is the OpenSpec change archiving workflow?▼

The OpenSpec change archiving workflow checks artifact and task completion status, optionally syncs delta-specs, and moves the completed change into a dated directory to preserve history.

How do I check artifact and task status before archiving an OpenSpec change?▼

You can check artifact and task completion status by using openspec commands within the workflow, which verifies that all implementation tasks are finished before archiving proceeds.

Do I need to sync delta-specs before archiving an OpenSpec change?▼

Syncing delta-specs is optional but recommended during OpenSpec archiving; the workflow will prompt you to perform delta-spec synchronization before moving the change into the archive directory.

Can I select an active OpenSpec change to archive if I don't specify a name?▼

Yes, if you do not specify a change name, the workflow will prompt you to select from active OpenSpec changes, allowing you to choose the correct completed change for archiving.

Why does archiving OpenSpec changes prevent rework?▼

Archiving OpenSpec changes prevents rework by moving completed artifacts into a dated archive directory, preserving the history and configuration while removing them from active workflow status.

Related Skills

Explore More Software Engineering Skills→
TranVanTienDatTranVanTienDat

openspec-archive-change

Archive completed changes with openspec CLI after completion checks.

Community
Intermediate
wtg42wtg42

openspec-archive-change

Archive openspec change directories after confirming task and artifact completion.

Community
Advanced
paradox123paradox123

openspec-archive-change

Archive completed OpenSpec changes with delta-spec sync and artifact checks.

Community
Advanced
KisthannyKisthanny
1

openspec-archive-change

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

Community
Advanced