openspec-archive-change

Archive completed experimental workflow changes with artifact and task checks.

47|2|Updated Oct 30, 2023
One-click install
npx skills add https://github.com/runtime-env/runtime-env --skill openspec-archive-change-runtime-env
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/runtime-env/runtime-env/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/runtime-env/runtime-env --skill openspec-archive-change-runtime-env

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed changes in an experimental workflow can be error-prone and difficult to trace. This skill provides a reproducible, auditable process to move a finished change into an archive, ensuring provenance and recoverability.

Core Features & Use Cases

  • Change selection and validation: prompts for the change to archive and checks artifact and task completion status.
  • Delta-spec assessment: evaluates whether there are delta specs and optionally synchronizes them with main specs before archiving.
  • Preservation and traceability: preserves configuration files (including .openspec.yaml) during archive and creates a dated archive directory.
  • Summary reporting: returns a clear archive summary with location, status, and any warnings for incomplete tasks or artifacts.

Quick Start

Use the openspec-archive-change skill to archive a completed change from the experimental workflow.

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 completed changes in an openspec workflow, select the change, validate artifact and task completion, synchronize delta specs, and move it into a dated archive directory while retaining configuration files like .openspec.yaml.

What happens to delta specs when archiving a change?

Delta specs are evaluated during the change archiving process and optionally synchronized with main specs before the final move to ensure your workflow artifacts remain consistent and traceable.

How does artifact status validation work before archiving experimental changes?

Artifact status validation checks whether all associated tasks and artifacts are completed before archiving, warning you about incomplete items to ensure only fully validated changes are moved into the archive.

Can I preserve configuration files when moving a change to the archive?

Yes, the archiving process preserves configuration files, including .openspec.yaml, ensuring provenance and recoverability while creating a dated archive directory for your completed change.

What is the best way to ensure traceability when archiving workflow changes?

The best way to ensure traceability is using a reproducible archiving process that generates a summary report with location and status, moving validated changes into a dated directory while preserving configuration.

Why does my change archiving process warn about incomplete tasks?

Your change archiving process warns about incomplete tasks because it enforces status checks on all associated artifacts and tasks, preventing the accidental archival of unvalidated or unfinished workflow changes.