openspec-archive-change

Validate task completion and sync specs before archiving OpenSpec changes.

Updated Jan 26, 2026

Search Tags:#workflow #archive #change management #task validation #openspec #spec sync

Ready to run

npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-archive-change-brandon-setegn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/brandon-setegn/kafka-test/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-archive-change-brandon-setegn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely finalize an implementation change by checking completion status, reviewing remaining tasks, and deciding whether to sync specs before archiving.

Core Features & Use Cases

Change Selection: Lists available active changes when the target change is not already known.
Completion Validation: Checks artifact status and task completion to warn about unfinished work before archive.
Spec Sync Assessment: Compares delta specs against main specs and supports syncing before archive when needed.
Archiving Workflow: Moves the completed change into the archive directory with a dated, organized target path.

Quick Start

Ask the skill to archive the completed change named openspec-archive-change after verifying its status and syncing specs if needed.

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 an OpenSpec change after implementation is complete?▼

You can archive a completed change by validating artifact status and task completion, then syncing delta specs against main specs before moving the change directory into a dated, organized archive path.

What happens to unfinished tasks when archiving a change in OpenSpec?▼

The skill checks task completion and warns about unfinished work before archiving. This validation step ensures incomplete changes are flagged rather than silently moved to the archive.

Do I need to sync specs before archiving an OpenSpec change?▼

Spec synchronization is assessed before archiving. The skill compares delta specs against main specs and supports syncing them if needed, ensuring the archive reflects the finalized spec state.

Can I archive a specific OpenSpec change without listing all active changes?▼

If the target change is already known, the skill archives it directly. When the target is not specified, it lists available active changes for selection before proceeding with the validation and archiving workflow.

What do I need to use the OpenSpec change archiving workflow?▼

You need the openspec CLI and access to change directories, tasks files, and delta specs for review and relocation. These components are required to validate completion status and move the change into the archive.

Why does archiving a change require spec synchronization checks?▼

Spec synchronization checks are required during archiving to ensure delta specs match main specs before relocation. This prevents archiving changes with outdated or conflicting specification data, maintaining archive integrity.