openspec-archive-change

Validate artifacts and tasks before archiving openspec experimental changes.

6|2|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/LingoJack/jcli --skill openspec-archive-change-lingojack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/LingoJack/jcli/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/LingoJack/jcli --skill openspec-archive-change-lingojack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you finalize and archive a completed change in an experimental workflow while checking for unfinished artifacts, incomplete tasks, and whether delta specs need to be synced to the main specs.

Core Features & Use Cases

  • Guided change selection: Prompts the user to select an active change when a change name is not provided, using openspec CLI JSON output.
  • Completion validation with confirmations: Verifies artifact completion via openspec status and checks tasks.md for incomplete checklist items, prompting for confirmation if anything is not done.
  • Delta spec sync assessment: Detects delta specs, compares them to corresponding main specs, produces a combined summary, and prompts whether to sync before archiving.
  • Deterministic archival action: Moves the change directory into an archive folder using a date-stamped name, failing safely if the target already exists.
  • Clear post-run reporting: Outputs the archived location, schema used, sync outcome, and any warnings encountered.

Quick Start

Ask the assistant to archive a completed change in the experimental workflow, including syncing delta specs if needed: Archive my completed change "CHANGE_NAME" in the openspec 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 spec changes in an openspec workflow?

To archive completed spec changes, the workflow validates artifacts and tasks, assesses delta spec sync needs against main specs, and moves the change directory into a date-stamped archive folder with clear success or error handling.

What happens if I try to archive an openspec change with incomplete tasks?

When archiving an openspec change with incomplete tasks, the process checks tasks.md for incomplete checklist items and prompts the user for confirmation before proceeding with the archive move.

Do I need to sync delta specs to main specs before archiving a completed change?

You do not need to sync manually beforehand; the archival process detects delta specs, compares them to corresponding main specs, produces a combined summary, and prompts you to decide whether to sync before archiving.

Can I archive an openspec experimental change without specifying its name?

Yes, you can archive an openspec experimental change without a name because the workflow uses openspec list JSON output to prompt interactive selection and confirmation of the active change.

Why does archiving a change directory fail safely in openspec?

Archiving a change directory fails safely to prevent data loss when the target date-stamped archive folder already exists, ensuring deterministic archival action and clear post-run reporting of any warnings encountered.