openspec-archive-change

Archive completed changes while preserving .openspec.yaml configuration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow to finalize and store it for future reference.

Core Features & Use Cases

  • Prompt-based change selection for archiving from openspec/changes.
  • Validation of artifact and task completion with optional user confirmation.
  • Delta-spec synchronization assessment and optional syncing before archiving.
  • Safe archival: preserves .openspec.yaml, creates openspec/changes/archive, and reports a clear summary.

Quick Start

Select an active change and follow the prompts to archive it.

Frequently Asked Questions about openspec-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Can I archive openspec changes without syncing the delta spec?

Delta spec synchronization is assessed during the archiving process to verify alignment. You can optionally sync the delta spec before archiving a change, or choose to skip synchronization if the current state is already finalized.

Does archiving an openspec change preserve the .openspec.yaml configuration file?

The archiving process validates artifact completion and task completion before finalizing a change. It applies guardrails to ensure all required tasks are finished, prompting for user confirmation before proceeding with the archival operation.

Why do I need to verify artifact and task completion before archiving openspec changes?

Yes, archiving an openspec change preserves the .openspec.yaml configuration file. The safe archival process creates the openspec/changes/archive directory, maintains the configuration file, and reports a clear summary of the completed operation.

What is the best way to manage completed change archives in an openspec project?

Verifying artifact and task completion before archiving openspec changes ensures that all required deliverables are finished. These guardrails prevent incomplete work from being finalized and moved into the archive location accidentally.

What is the best way to manage completed change archives in an openspec project?

The best way to manage completed change archives is using an automated archival workflow that moves finalized changes into openspec/changes/archive. This approach validates completion, assesses delta spec synchronization, and preserves configuration files automatically.