openspec-archive

Archive completed OpenSpec changes and update affected specification files.

151|20|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill openspec-archive-arman-kudaibergenov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive
Source: https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/main/.claude/skills/openspec-archive
Command: npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill openspec-archive-arman-kudaibergenov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves the need to reliably archive completed OpenSpec changes while keeping the official specifications in sync, reducing the risk of outdated or conflicting spec documentation.

Core Features & Use Cases

  • Archives completed OpenSpec change folders: Moves a finished openspec/changes/<id>/ entry into openspec/changes/archive/<id>/ after verifying tasks are completed.
  • Updates spec files from spec deltas: Applies any recorded spec deltas to the corresponding files in openspec/specs/.
  • Validates the final state: Performs a sanity check to ensure the archive move and spec updates resulted in a consistent repository state.

Quick Start

Ask the AI to archive a completed OpenSpec change by running the skill with the change identifier provided in your OpenSpec workflow.

Frequently Asked Questions about openspec-archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive completed OpenSpec changes and update specification documents?

You can archive completed OpenSpec changes by selecting a specific change-id, verifying all tasks in tasks.md are marked complete, moving the folder to openspec/changes/archive/, and applying spec deltas to update openspec/specs/ files.

When should I run the OpenSpec archiving workflow for a repository change?

You should run the OpenSpec archiving workflow at the end of an implementation cycle, especially after successfully executing openspec-apply, to move completed change folders and sync specification documents.

What happens if OpenSpec change tasks are not fully completed before archiving?

The archiving process checks tasks.md for all [x] markers to ensure completion. If tasks are incomplete, the workflow validates the change is not complete and prevents moving the folder to the archive directory.

How does specification synchronization work when archiving OpenSpec changes?

Specification synchronization applies recorded spec deltas to the corresponding files in openspec/specs/ during the archive process, ensuring the official specification documents reflect the completed changes accurately.

Does OpenSpec archiving validate the repository state after moving changes?

Yes, the workflow performs a sanity check to validate that the archive move and spec updates resulted in a consistent repository state, ensuring the resulting files exist and align correctly.

Can I use OpenSpec archiving for repository hygiene without manual file management?

Yes, the workflow automates repository hygiene by moving finished change folders into openspec/changes/archive/<id>/, applying spec delta outputs, and validating file alignment without manual intervention.