openspec-archive-change

Archive completed openspec changes after verifying artifacts and tasks.

2.6k|399|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/Soju06/codex-lb --skill openspec-archive-change-soju06
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Soju06/codex-lb/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/Soju06/codex-lb --skill openspec-archive-change-soju06

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Automated Archiving: Moves completed changes 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 specifications.
  • Use Case: After implementing a new feature and testing all its components, use this Skill to formally archive the change, marking it as complete and organized.

Quick Start

Use the openspec-archive-change skill to archive the change named 'user-profile-update'.

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 a completed change in an experimental workflow?

To archive a completed change, this Skill moves the finalized artifacts to a designated archive location after verifying task completion and assessing delta spec synchronization. It uses the openspec CLI to check statuses and prompts you to select and confirm the specific change to archive.

What is delta spec synchronization and how does it affect archiving changes?

Delta spec synchronization assesses whether the specifications for a completed change align with main project specifications before archiving. The Skill evaluates this sync status and optionally updates the main specs to ensure a clean and organized project history.

Do I need the openspec CLI to archive completed changes?

Yes, the openspec CLI is required to archive completed changes. The Skill depends on the CLI to perform status checks and list available changes, ensuring that all artifacts and tasks are verified as complete before the archiving process executes.

Can I verify artifact and task completion before moving changes to the archive?

Yes, status verification is a core feature that checks artifact and task completion before archiving. This prevents incomplete work from being archived and requires user confirmation to proceed with moving the selected change.

What happens if a change is not fully completed when I try to archive it?

The archiving process verifies artifact and task completion before proceeding. If the openspec CLI status checks detect incomplete tasks, the Skill prevents the change from being archived until those components are resolved and verified.

When should I formally archive a change in my version control workflow?

You should archive a change after implementing a new feature and testing all its components. This marks the change as complete, organizes the project history, and ensures delta specifications are synchronized with the main specifications.