openspec-archive-change

Archive completed OpenSpec changes with delta spec synchronization.

Updated Nov 12, 2025
One-click install
npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-archive-change-artagon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/artagon/artagon-vscode-profiles/tree/main/agents/skills/openspec-archive-change
Command: npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-archive-change-artagon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you finalize an OpenSpec experimental workflow by archiving a completed change while ensuring required artifacts and tasks are complete, and optionally syncing delta specs back to the main specs.

Core Features & Use Cases

  • Change discovery & selection: Lists available active changes and prompts you to choose when a change name is not provided, avoiding unsafe guesses.
  • Completion validation with confirmations: Checks artifact completion via openspec status --change "<name>" --json and inspects tasks.md for incomplete tasks, prompting for confirmation instead of blocking.
  • Delta spec assessment & optional sync: Detects delta specs and computes what would be added/modified/removed/renamed versus the main specs, then offers sync or archive-only options.
  • Deterministic archive move with guardrails: Moves openspec/changes/<name> into openspec/changes/archive/YYYY-MM-DD-<name>/, failing if the target already exists to prevent overwrites.
  • Clear operational summary: Reports the schema used, archive location, and whether specs were synced or skipped.

Quick Start

Archive the selected completed change after checking artifacts and delta specs by running the openspec-archive-change skill without a change name so you can choose from the active list.

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?

To archive completed OpenSpec changes safely, the skill validates artifact completion via CLI JSON status output and moves the change directory to a date-prefixed archive folder while preserving .openspec.yaml configurations.

What happens to delta specs when an OpenSpec workflow is archived?

When an OpenSpec workflow is archived, delta specs are reconciled against main specs to compute additions, modifications, and removals. Users can sync deltas back to main specs or archive the change without syncing.

Can I finalize an OpenSpec change if some tasks in tasks.md are incomplete?

Yes, finalizing an OpenSpec change with incomplete tasks prompts for user confirmation rather than blocking the process. The skill detects incomplete items in tasks.md and asks whether to proceed with the archival.

How does OpenSpec prevent archive directory overwrites during workflow archival?

OpenSpec prevents archive overwrites by moving the change directory into openspec/changes/archive/YYYY-MM-DD-name/ and failing deterministically if the target directory already exists, ensuring no previous archives are lost.

Do I need to specify a change name to archive an OpenSpec experimental workflow?

No, providing a change name is optional. If omitted, the skill lists available active OpenSpec changes and prompts you to select one, avoiding unsafe guesses during the workflow archival process.