openspec-archive-change

Archive completed OpenSpec change directories to a dated location.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-archive-change-jankneumann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-archive-change-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines finalizing and archiving completed OpenSpec workflow changes by verifying completion, prompting the user for confirmation on warnings, optionally syncing delta specs, and moving the change into a dated archive directory so workspaces remain tidy and auditable.

Core Features & Use Cases

  • Interactive change selection: Prompts the user to choose an active change when none is provided, never guessing on their behalf.
  • Completion verification: Uses openspec CLI status JSON to verify artifact completion and reads tasks.md to count incomplete tasks, surfacing warnings and requiring explicit confirmation to proceed.
  • Delta spec assessment and sync: Detects delta specs under openspec/changes/<name>/specs, summarizes proposed spec changes versus main specs, offers to sync (recommended), and leverages the openspec-sync-specs approach if requested.
  • Safe archival: Creates openspec/changes/archive, generates a dated target name, checks for conflicts, moves the change while preserving .openspec.yaml, and reports a clear archive summary including any warnings.

Quick Start

Archive the change named "my-feature" after confirming any warnings and syncing delta specs if recommended.

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 without losing spec history?

To archive OpenSpec changes, the workflow validates artifact completion using CLI status JSON, checks tasks.md for pending tasks, prompts for confirmation on warnings, optionally syncs delta specs, and moves the directory to a dated archive while preserving .openspec.yaml.

What happens if I try to archive OpenSpec changes with incomplete tasks?

If incomplete tasks exist in tasks.md, the archival workflow surfaces warnings detailing the outstanding items and requires explicit user confirmation before moving the OpenSpec change directory to the archive.

Do I need the openspec CLI installed to archive change directories?

Yes, the openspec CLI is required to generate the list and status JSON output needed to validate artifact completion and assess delta specs before moving the change directory to the dated archive.

How does delta spec sync work when finalizing OpenSpec workflow changes?

Delta spec sync detects proposed changes under openspec/changes/<name>/specs, summarizes the differences against main specs, and leverages the openspec-sync-specs approach to merge updates before moving the change to the archive.

Can I automatically archive multiple OpenSpec changes at once?

No, the archival workflow prompts the user to interactively choose an active change when none is provided and never guesses on their behalf, ensuring each OpenSpec change is validated and archived individually with explicit confirmation.