openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and syncing delta specs.

10|3|Updated Apr 1, 2018
One-click install
npx skills add https://github.com/kaishin/redalemeden.com --skill openspec-archive-change-kaishin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/kaishin/redalemeden.com/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/kaishin/redalemeden.com --skill openspec-archive-change-kaishin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed OpenSpec change in the experimental workflow to finalize work and preserve artifacts for reference.

Core Features & Use Cases

  • Interactive change selection: prompts user to choose an active change when a name is not provided.
  • Artifact and task validation: checks completion status via openspec status and tasks.md.
  • Delta spec sync assessment: compares delta specs to main specs and prompts for sync or archive.
  • Safe archiving: moves the change into openspec/changes/archive/YYYY-MM-DD-<name> while preserving .openspec.yaml.

Quick Start

Archive a completed OpenSpec change by validating artifacts, optionally syncing delta specs, and moving the change to the dated archive path.

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 a completed OpenSpec change safely?

To archive an OpenSpec change, the workflow validates artifact completion via `openspec status`, optionally syncs delta specs, and moves the change folder to `openspec/changes/archive/YYYY-MM-DD-<name>` while preserving `.openspec.yaml`.

What happens if I try to archive an OpenSpec change with incomplete artifacts?

If artifacts are incomplete, the workflow alerts you using `openspec status --change <name> --json` and prompts for confirmation before proceeding with the archiving process to prevent data loss.

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

Yes, the workflow reviews tasks from `tasks.md` and delta specs under `openspec/changes/<name>/specs/`, performing an optional sync via the Task tool before moving the change to the archive directory.

How do I select which OpenSpec change to archive if I have multiple active changes?

If no change name is provided, the workflow uses `openspec list --json` to enumerate all active changes and interactively prompts you to select the specific change you want to archive.

Do I need to manually check task completion before archiving an OpenSpec change?

No, the workflow automatically checks artifact completion and reviews `tasks.md` for you, alerting you to incomplete items and prompting for confirmation to proceed with archiving if needed.