openspec-archive-change

Archive completed OpenSpec changes with safety checks and optional spec synchronization.

1|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-archive-change-cynkra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/cynkra/cynkra.ai.day/tree/main/indietypst/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-archive-change-cynkra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you finalize an OpenSpec experimental change by safely archiving it only after you review completion status, optional task checklists, and any pending delta-spec differences.

Core Features & Use Cases

  • Change selection & validation: Prompts you to choose a specific active change when a change name isn’t provided, preventing accidental archiving.
  • Completion checks before archiving: Verifies artifact completion via OpenSpec status and scans tasks.md for incomplete tasks, prompting for confirmation if anything is unfinished.
  • Delta spec assessment & optional sync: Detects delta specs and compares them against main capability specs, summarizes needed sync actions, and offers “sync then archive” versus “archive without syncing.”
  • Deterministic archive placement: Moves the change directory into openspec/changes/archive using a date-stamped folder name, and provides a clear post-archive report.

Quick Start

Use the openspec-archive-change skill to archive your completed change by name and, if delta specs exist, optionally sync them to the main specs before 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 safely?

You can sync delta specs to main capability specs by choosing the sync then archive option, which compares openspec/changes/<name>/specs against main specs before moving the change to the archive directory.

What happens if my OpenSpec change has incomplete tasks.md checklists?

If tasks.md contains incomplete tasks, the archiving process detects this and prompts you for confirmation before proceeding, preventing accidental closure of unfinished workflow changes.

How does delta spec synchronization work when finalizing an OpenSpec change?

Delta spec synchronization compares delta specs under openspec/changes/<name>/specs against main capability specs, summarizes needed sync actions, and offers options to sync then archive or archive without syncing.

Can I archive an OpenSpec change without providing a specific change name?

Yes, when a change name is not provided, the process prompts you to select a specific active change from the available list, preventing accidental archiving of the wrong workflow artifact.

Where are archived OpenSpec changes stored and how are they named?

Archived OpenSpec changes are moved deterministically into openspec/changes/archive using a date-stamped folder name formatted as YYYY-MM-DD-<name>, ensuring consistent artifact placement and a clear post-archive report.

When should I not archive an OpenSpec experimental change?

You should not archive an OpenSpec change when artifact completion checks fail via OpenSpec status or tasks.md has pending incomplete tasks, as the workflow requires a consistent state before finalization.