openspec-archive-change

Archive completed changes after validating artifacts and syncing delta specs.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/TbK0ng/silver-bullet-kernel --skill openspec-archive-change-tbk0ng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/TbK0ng/silver-bullet-kernel/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/TbK0ng/silver-bullet-kernel --skill openspec-archive-change-tbk0ng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you finalize and archive completed changes within the experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

  • Archive completed changes: Moves a completed change to an archive directory.
  • Artifact and task validation: Checks if all associated artifacts and tasks are completed before archiving.
  • Delta spec synchronization: Assesses and optionally syncs delta specifications with main specifications.
  • Use Case: After successfully implementing and testing a new feature, use this Skill to archive the associated change, marking it as complete and organized.

Quick Start

Use the openspec-archive-change skill to archive the change named 'new-user-auth'.

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

To archive completed changes in an OpenSpec workflow, use the archive skill to validate associated artifacts and tasks, assess delta spec synchronization, and move the finalized change to an archive directory.

What is delta spec synchronization and when do I need it during change archiving?

Delta spec synchronization assesses and optionally syncs delta specifications with main specifications during change archiving. You need it to ensure experimental workflow changes are finalized and aligned before moving to the archive directory.

Does the OpenSpec archive process validate artifacts and tasks before completion?

Yes, the OpenSpec archive process validates artifacts and tasks by checking if all associated items are completed before archiving. It requires the openspec CLI for status checks and prompts for user confirmation before finalizing the move.

Do I need the openspec CLI to archive a completed change?

Yes, you need the openspec CLI installed to archive a completed change. The CLI is required to perform status checks, list available changes, and assess delta spec synchronization before moving the finalized change to the archive directory.

Can I skip user confirmation when moving changes to the archive directory?

No, you cannot skip user confirmation when moving changes to the archive directory. The workflow explicitly prompts for user confirmation after checking task completion and delta spec synchronization to ensure a clean project history.