openspec-archive-change

Archive completed OpenSpec changes with timestamped paths and optional syncing.

208|148|Updated Oct 27, 2021
One-click install
npx skills add https://github.com/elastic/terraform-provider-elasticstack --skill openspec-archive-change-elastic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/elastic/terraform-provider-elasticstack/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/elastic/terraform-provider-elasticstack --skill openspec-archive-change-elastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes after implementation, ensuring traceable history and organized records.

Core Features & Use Cases

  • End-to-end archival of an OpenSpec change, including artifact status checks and delta-spec synchronization.
  • Optional delta-spec alignment before archiving to keep main specs in sync.
  • Preservation of metadata and the .openspec.yaml alongside archived changes to aid future restoration.

Quick Start

Provide the change name or select from available changes to begin archiving.

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 after implementation?

You can archive completed OpenSpec changes by selecting the change name and confirming the archiving process. The workflow checks artifact status, validates delta-specs, and moves the change to a timestamped archive path to preserve history.

What does delta-spec synchronization do before archiving an OpenSpec change?

Delta-spec synchronization aligns your main specs with the completed change before archiving. This optional step ensures your primary OpenSpec specifications remain updated and consistent with the implemented modifications.

How are OpenSpec artifacts and metadata preserved during the archiving process?

The archiving process preserves metadata and the .openspec.yaml file alongside the archived changes. This ensures traceable history and organized records, aiding future restoration if you need to retrieve the completed change.

When should I run an OpenSpec status check before archiving a change?

You should run an OpenSpec status check before archiving to verify that all artifacts and delta-specs have passed validation. This ensures the change is fully implemented and ready for safe, organized archival.

Can I use workflow automation to archive OpenSpec changes without manual selection?

You must provide the change name or select from available changes to begin archiving. The workflow automation requires this prompt to identify the correct completed change and confirm the archiving action.