openspec-archive-change

Archive completed changes in an experimental workflow using the openspec CLI.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/bharathwaaj/numlox --skill openspec-archive-change-bharathwaaj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/bharathwaaj/numlox/tree/main/.agent/skills/openspec-archive-change
Command: npx skills add https://github.com/bharathwaaj/numlox --skill openspec-archive-change-bharathwaaj

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of archiving completed changes in the experimental workflow, ensuring a smooth transition from implementation to archiving.

Core Features & Use Cases

  • Change Selection: Allows users to select a specific change to archive, or automatically infers the change from context if not specified.
  • Artifact and Task Completion Check: Verifies that all artifacts and tasks are complete before archiving.
  • Spec Sync Assessment: Evaluates the need for syncing delta specs with main specs before archiving.
  • Archive Creation: Creates an archive directory and moves the change to it, with a timestamped name.

Quick Start

Archive the change with the name 'change123'.

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 the openspec workflow?

To archive completed changes in the openspec workflow, you select a specific change, verify artifact and task completion, assess spec synchronization status, and execute the archive operation to move it to a timestamped directory.

What does spec synchronization assessment check before archiving a change?

Spec synchronization assessment evaluates whether delta specs need syncing with main specs before archiving. This ensures the archived workflow directory maintains accurate documentation of completed changes and prevents data inconsistencies.

Can I automatically infer which change to archive without specifying the name?

Yes, you can automatically infer the change from context if not explicitly specified. The workflow allows selecting a specific change by name or automatically determining the correct change based on the current workflow context.

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

Yes, you need the openspec CLI and appropriate permissions to modify the workflow directory. The archiving process relies on the openspec CLI to verify completion status and create the timestamped archive directory.

What happens if artifacts and tasks are not complete when archiving changes?

The archiving process verifies that all artifacts and tasks are complete before proceeding. If completion checks fail, the archive operation is prevented to ensure only fully implemented changes are moved to the archive directory.

When should I use automated change archiving instead of manual file moves?

Automated change archiving is best when finalizing completed changes in the experimental workflow. It ensures proper spec synchronization, validates task completion, and creates timestamped archive directories that manual file moves cannot guarantee.