skills.rest
vuthuonghai-steve
vuthuonghai-steveCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed change directories to openspec/changes/archive with optional delta-spec sync.

Updated Aug 27, 2026
Search Tags:#automation#workflow#archive#openspec#artifact-status#delta-specs#change-archiving
One-click install
npx skills add https://github.com/vuthuonghai-steve/KLTN --skill openspec-archive-change-vuthuonghai-steve
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/vuthuonghai-steve/KLTN/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/vuthuonghai-steve/KLTN --skill openspec-archive-change-vuthuonghai-steve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow to finalize and store it for reference.

Core Features & Use Cases

  • Archive completed changes after implementation is verified.
  • Validate artifact and task completion via openspec status and tasks, with optional delta-spec synchronization.
  • Move the change directory to an organized archive location while preserving configuration files.

Quick Start

Prompt for a change name if needed, verify artifacts and tasks, assess delta specs, and move the change into openspec/changes/archive/YYYY-MM-DD-<name>.

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

Archiving completed changes in openspec involves verifying artifact and task status, optionally syncing delta specs, and moving the change directory to an archive path to preserve metadata for traceability.

What does delta-spec synchronization do during change archiving?▼

Delta-spec synchronization aligns delta specs before moving the change directory to the archive, ensuring the finalized implementation reflects all verified modifications and preserving metadata for traceability.

When should I finalize and archive an openspec change?▼

You archive an openspec change when implementation is verified, artifact and task statuses pass validation, and the workflow needs finalizing to store the change directory for reference and traceability.

Does the openspec archiving process preserve configuration files?▼

Yes, the openspec archiving process preserves configuration files by moving the finished change directory to an organized archive location while maintaining the existing configuration structure.

What is the best way to structure archived openspec changes for traceability?▼

The best way to structure archived openspec changes for traceability is moving the completed change directory to openspec/changes/archive/YYYY-MM-DD-<name>, which preserves metadata and configuration files.

Why does openspec change archiving require verifying artifact and task completion?▼

Verifying artifact and task completion is required during openspec change archiving to ensure the implementation is fully finalized and validated before moving the directory to the archive path.

Related Skills

Explore More Software Engineering Skills→
Pony-UnicornPony-Unicorn
7

openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

Community
Advanced
rock-hurock-hu

openspec-archive-change

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

Community
Advanced
LeonardoTan19LeonardoTan19
2

frontend-page

Assemble frontend pages from design docs using shadcn components and generated API types.

Community
Advanced
MiDouTechMiDouTech

openspec-archive-change

Archive completed openspec changes into date-prefixed directories after verification.

Official
Advanced