skills.rest
kamansoft
kamansoftOFFICIAL
Explore all skills by this author →
Website𝕏@kamansoftGitHub

openspec-archive-change

Archive completed experimental workflow changes with optional delta spec syncing.

Updated Mar 23, 2026
Search Tags:#archiving#change management#change tracking#specification sync#workflow completion
One-click install
npx skills add https://github.com/kamansoft/vite-plugin-flatwave-react --skill openspec-archive-change-kamansoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/kamansoft/vite-plugin-flatwave-react/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/kamansoft/vite-plugin-flatwave-react --skill openspec-archive-change-kamansoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill aids in archiving completed changes in the experimental workflow, ensuring changes are safely stored and finalized upon implementation completion.

Core Features & Use Cases

  • Archive Completed Changes: Securely stores changes once implementation is complete.
  • Check Completion Status: Verify all artifacts and tasks are finished before archiving.
  • Optional Spec Sync: Provides the option to sync delta specs with main specs before archiving.

Quick Start

Archive a completed change by selecting it and confirming any outstanding tasks or artifacts. If delta specs are present, choose whether to sync them with the main specs or archive without syncing.

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 changes in an experimental workflow?▼

Archiving completed changes requires selecting the finished change and verifying all tasks and artifacts are complete, with an option to sync delta specifications before final archival.

Do I need the openspec CLI to track and finalize change status?▼

Yes, the openspec CLI is required to check change status and manage the archival process for finalizing completed changes in the experimental workflow.

What happens to delta specifications when I finalize change tracking?▼

When finalizing change tracking, delta specifications can be optionally synced with main specs, ensuring documentation is updated before the change is safely archived.

Can I verify completion status before archiving workflow changes?▼

Yes, the Skill checks the completion status of all artifacts and tasks before archiving, ensuring workflow changes are only finalized when implementation is fully complete.

What is the best way to sync delta specifications with main specs?▼

The best way to sync delta specifications is during the change archival process, where you can choose to merge delta specs with main specs or archive the change without syncing.

Related Skills

Explore More Software Engineering Skills→
goerngoern
113

openspec-new-change

Scaffold OpenSpec change directories and track artifact readiness.

Community
Advanced
minhquan2904minhquan2904

sync-task

Align OpenSpec change documentation with current source code and report drift.

Community
Advanced
memorysavermemorysaver

openspec-continue-change

Create the next OpenSpec workflow artifact via the openspec CLI.

Community
Advanced
MaplumeXMaplumeX

openspec-archive-change

Archive completed openspec changes with validation and delta-spec synchronization checks.

Community
Advanced