skills.rest
zabiny
zabinyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta-spec status.

2|2|Updated Sep 20, 2023
Search Tags:#workflow#cli#archive#openspec#change-management#delta-spec#artifact-status
One-click install
npx skills add https://github.com/zabiny/klabis --skill openspec-archive-change-zabiny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/zabiny/klabis/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/zabiny/klabis --skill openspec-archive-change-zabiny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes from the experimental workflow, preserving provenance and enabling audits.

Core Features & Use Cases

  • Prompt for a change name when not provided
  • Validate artifact and task completion, assess delta-spec synchronization
  • Archive the change under openspec/changes/archive/YYYY-MM-DD-<name> with metadata preserved

Quick Start

Provide a change name to archive after confirming artifacts and tasks.

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

To archive OpenSpec changes, the workflow validates artifact and task completion, checks delta-spec synchronization, then moves files safely into openspec/changes/archive/YYYY-MM-DD-<name> while preserving metadata. It requires the OpenSpec CLI to execute these steps.

What does delta-spec synchronization mean in change management workflows?▼

Delta-spec synchronization compares the change's delta specs against the baseline to ensure all modifications are tracked and consistent. The workflow assesses this status before archiving an OpenSpec change to prevent unresolved spec drift.

Do I need the OpenSpec CLI to archive changes in the experimental workflow?▼

Yes, the OpenSpec CLI is required to archive completed changes. The workflow depends on it to validate artifact and task completion, assess delta-spec status, and execute safe file movement into the archive directory.

What happens if artifacts or tasks are not completed before archiving an OpenSpec change?▼

The workflow validates artifact and task completion before proceeding with archiving. If checks fail, the change is not moved to the archive directory, preventing incomplete changes from being archived and ensuring provenance integrity.

Can I archive a change without providing a specific change name?▼

You can initiate archiving without a change name, but the workflow will prompt you to provide one. The change name is required to construct the archive directory path as openspec/changes/archive/YYYY-MM-DD-<name>.

When should I archive completed changes instead of keeping them in the active directory?▼

You should archive changes after confirming all artifacts and tasks are completed and delta specs are synchronized. Archiving preserves provenance, enables audits, and keeps the active OpenSpec workspace uncluttered.

Related Skills

Explore More Software Engineering Skills→
danielsogldanielsogl
39

openspec-archive-change

Archive completed OpenSpec changes after validating delta-spec synchronization.

Community
Advanced
rock-hurock-hu

openspec-archive-change

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

Community
Advanced
cogidoocogidoo

openspec-archive-change

Archive completed OpenSpec changes with date-based naming after validation.

Community
Advanced
accidental-hedge-fundaccidental-hedge-fund
3

openspec-archive-change

Archive completed openspec experimental changes to dated directories with validation.

Official
Intermediate