openspec-archive-change

Archive completed OpenSpec change directories after verifying artifacts and tasks.

30|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/pacaplan/flokay --skill openspec-archive-change-pacaplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/pacaplan/flokay/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/pacaplan/flokay --skill openspec-archive-change-pacaplan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed development changes within the OpenSpec workflow, ensuring a clean and organized project history.

Core Features & Use Cases

  • Automated Archiving: Moves completed change directories to a designated archive location.
  • Status Verification: Checks artifact and task completion before archiving.
  • Delta Spec Sync: Assesses and optionally syncs delta specifications with main specs.
  • Use Case: After successfully implementing a new feature and merging it, use this Skill to archive the associated change files, keeping your active development directory tidy.

Quick Start

Use the openspec-archive-change skill to archive the change named 'feature-x'.

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 development changes in an OpenSpec workflow?

To archive completed development changes in an OpenSpec workflow, this skill verifies that all tasks and artifacts are complete, assesses delta spec synchronization, and moves the change directory to a designated archive location after user confirmation.

What happens to delta specs when archiving a completed OpenSpec change?

When archiving a completed OpenSpec change, the skill assesses delta spec synchronization status and optionally synchronizes delta specifications with main specs before moving the change directory to the archive.

Do I need the OpenSpec CLI to archive change directories?

Yes, you need the OpenSpec CLI installed to archive change directories, as this skill requires it to perform status checks and delta specification synchronization operations before archiving.

Can I move a development change to the archive if tasks are not verified?

You cannot move a development change to the archive if tasks are not verified, because this skill checks artifact and task completion status prior to archiving to ensure a clean and organized project history.

When should I archive completed change files in version control?

You should archive completed change files in version control after successfully implementing a new feature and merging it, which keeps your active development directory tidy by moving associated artifacts to an archive.