openspec-archive-change

Archive completed OpenSpec changes with delta spec synchronization and summaries.

4.1k|508|Updated Jul 11, 2023
One-click install
npx skills add https://github.com/MetaCubeX/metacubexd --skill openspec-archive-change-metacubex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/MetaCubeX/metacubexd/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/MetaCubeX/metacubexd --skill openspec-archive-change-metacubex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the OpenSpec workflow to preserve artifacts and enable audit trails.

Core Features & Use Cases

  • Archive completed changes to a structured archive directory.
  • Validate artifact and task completion status before archiving.
  • Assess delta spec synchronization with main specs to ensure consistency.
  • Generate clear archival summaries with location and status.

Quick Start

Run the openspec archive command to archive a completed change, providing the change name if prompted. Example: openspec archive change <name>.

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

To archive completed OpenSpec changes, run the openspec archive command with the change name. It validates artifact and task completion status before moving the change to the openspec/changes/archive directory and generating a concise summary.

When do I need to archive changes in the OpenSpec workflow?

You need to archive changes in the OpenSpec workflow when a change has passed validation and requires preservation for audit trails. Archiving moves the completed artifacts to a structured directory to maintain project history and consistency.

Does the OpenSpec archive process check task completion before archiving?

Yes, the OpenSpec archive process validates both artifact and task completion status before archiving. This ensures only fully completed changes are moved to the openspec/changes/archive directory for reliable audit trails.

What is the best way to sync delta specs with main specs during change archiving?

The best way to sync delta specs is through the optional delta spec synchronization built into the OpenSpec archive command. It assesses delta spec synchronization with main specs during archiving to ensure overall spec consistency.

Can I use the openspec archive command without specifying a change name?

You can use the openspec archive command without immediately specifying a change name. The workflow will prompt you to provide the change name interactively if it is not supplied directly in the command line arguments.

Why does spec synchronization fail when archiving incomplete OpenSpec changes?

Spec synchronization and archiving fail for incomplete changes because the workflow validates artifact and task completion status first. This prevents partially finished changes from being archived and ensures the structural integrity of the audit trail.