openspec-archive-change

Archive completed openspec changes after verifying artifacts and tasks.

Updated Apr 11, 2025
One-click install
npx skills add https://github.com/pabloimrik17/monolab --skill openspec-archive-change-pabloimrik17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/pabloimrik17/monolab/tree/main/.junie/skills/openspec-archive-change
Command: npx skills add https://github.com/pabloimrik17/monolab --skill openspec-archive-change-pabloimrik17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams finalize and archive completed changes in an OpenSpec experimental workflow by verifying artifact and task completion, assessing delta spec differences, and moving the change to a dated archive location while preserving configuration.

Core Features & Use Cases

  • Verification: Uses openspec list and openspec status outputs to list active changes and confirm artifact completion before archiving.
  • Task and Spec Assessment: Checks tasks.md for incomplete tasks and compares delta specs against main specs to summarize additions, modifications, removals, or renames and offer an optional sync.
  • Safe Archival: Creates an archive folder, prevents overwrites by checking for existing targets, preserves .openspec.yaml, and requires explicit user confirmations for warnings.
  • Use Case: After implementing a feature or schema change, run this workflow to confirm all artifacts and tasks are complete, optionally sync specs, and archive the change into openspec/changes/archive/YYYY-MM-DD-<change>.

Quick Start

Archive the change named add-user-auth by verifying artifacts and tasks, optionally syncing delta specs, and moving it to openspec/changes/archive with a dated folder.

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

Archive OpenSpec changes by verifying artifact and task completion, optionally synchronizing delta specs, and moving the change directory to a dated archive folder. The workflow requires explicit user confirmation when warnings are present.

What does OpenSpec delta spec synchronization do before archiving?

Delta spec synchronization compares change-specific specs against main specs to summarize additions, modifications, removals, or renames. It offers an optional sync to update main specs before the change is moved to the archive.

Does archiving OpenSpec changes overwrite existing folders?

No, archiving OpenSpec changes prevents overwrites by checking for existing target folders before moving. It creates a dated archive location and preserves the .openspec.yaml configuration file during the move.

Do I need the openspec CLI to finalize and archive changes?

Yes, the openspec CLI is required to run list and status commands for verifying active changes and artifact completion. You also need filesystem move permissions to transfer the change directory to the archive.

What happens if tasks.md has incomplete tasks during OpenSpec archival?

When tasks.md contains incomplete tasks, the workflow identifies them and issues warnings. It requires explicit user confirmation to proceed with archiving the change despite the incomplete task status.