openspec-archive-change

Archive completed openspec changes after validating tasks and syncing delta specs.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/caelaxie/agenthub --skill openspec-archive-change-caelaxie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/caelaxie/agenthub/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/caelaxie/agenthub --skill openspec-archive-change-caelaxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finalizes and archives a completed change in the openspec experimental workflow, guiding the user through selection, validation, optional spec sync, and safe relocation of the change into a dated archive folder while preserving metadata.

Core Features & Use Cases

  • Guided selection: Prompts the user to choose an active change when no name is provided to avoid accidental archival.
  • Artifact and task validation: Uses openspec status output and task file parsing to detect incomplete artifacts or tasks and requests confirmation before proceeding.
  • Delta spec assessment and optional sync: Compares delta specs to main specs, summarizes additions, modifications, removals, and renames, and offers a recommended sync workflow prior to archiving.
  • Safe archival operations: Creates an archive directory using a date-prefixed name, checks for conflicts, moves the change directory atomically, and reports a clear completion summary. Use case: After implementation is complete for a feature change, run this Skill to confirm completion, optionally sync specs, and move the change into openspec/changes/archive with an audit-friendly name.

Quick Start

Use the openspec-archive-change skill to archive the change named my-feature-change after confirming any warnings.

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

To archive openspec changes, you select an active change, validate artifact and task completion via the openspec CLI, optionally sync delta specs, and move the change directory to a dated archive folder with explicit confirmation for incomplete items.

What happens to incomplete tasks when archiving an openspec change?

Incomplete tasks are detected using openspec status output and task file parsing, and the Skill requests explicit user confirmation before proceeding with the archival of any ambiguous or incomplete items.

Can I sync delta specs to main specs before archiving an openspec change?

Yes, delta specs are compared to main specs to summarize additions, modifications, removals, and renames, and a recommended sync workflow is offered prior to moving the change directory to the archive.

Do I need the openspec CLI to archive changes?

Yes, the openspec CLI is required for listing active changes and performing status checks, and repository file access is needed to compare tasks and specs during the archival validation process.

How are archived openspec changes named to avoid conflicts?

Archived changes use a date-prefixed name to create an audit-friendly directory, and the Skill checks for naming conflicts before atomically moving the change directory into openspec/changes/archive.