openspec-archive-change

Archive completed OpenSpec experimental changes into date-prefixed directories.

10.2k|702|Updated Apr 12, 2012

Search Tags:#workflow #versioning #CLI #archive #openspec #specs #change-management

Ready to run

npx skills add https://github.com/studyzy/imewlconverter --skill openspec-archive-change-studyzy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/studyzy/imewlconverter/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/studyzy/imewlconverter --skill openspec-archive-change-studyzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe, auditable workflow to archive completed experimental changes in OpenSpec, ensuring configurations, specs, and artifacts are preserved for reference and replay if needed.

Core Features & Use Cases

Archiving workflow: Move finished change directories to an archive folder with a date-based name, preserving metadata.
Delta spec sync assessment: Detect and summarize delta specs versus main specs; prompt decisions to sync or archive without syncing.
Validation checks: Verify artifact completion and task completion before archiving; offer user confirmation when incomplete.
Use Case: After finishing a feature change in OpenSpec, securely archive it for long-term traceability while keeping related specs accessible.

Quick Start

Archive a completed change by invoking the OpenSpec archiver for a change named my-change; ensure you have the OpenSpec CLI installed and follow the prompts to confirm archiving.

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 to preserve specs and artifacts?▼

To archive completed OpenSpec changes, the Skill moves the change directory into a date-prefixed archive folder. This workflow preserves metadata, delta specs, and associated artifacts for long-term traceability and replay.

Do I need the OpenSpec CLI installed to archive my feature changes?▼

Yes, you need the OpenSpec CLI installed to perform archival operations. The Skill leverages the CLI to move finished change directories to an archive folder with a date-based name while enforcing validation checks.

What happens to incomplete tasks and artifacts when archiving OpenSpec changes?▼

Before archiving OpenSpec changes, the Skill enforces validation checks to verify artifact and task completion. If items are incomplete, it prompts you for confirmation to proceed with archiving or halt the operation.

Can I sync delta specs with main specs before archiving an OpenSpec change?▼

Yes, the Skill detects and summarizes delta specs versus main specs. It prompts you to decide whether to sync changes into the main specs or archive the directory without syncing.

Why does my OpenSpec change directory need a date prefix in the archive folder?▼

A date-prefixed archive folder ensures safe, auditable organization of archived OpenSpec changes. This naming convention preserves metadata and configurations, making finished feature changes easy to locate for future reference.

What is the best way to manage versioning for experimental OpenSpec workflow changes?▼

The best way to manage versioning for experimental OpenSpec changes is using a validation and archival workflow. This process verifies task completion, assesses delta specs, and securely archives directories to maintain traceability.