openspec-archive-change

Archive completed changes with status checks and optional delta spec sync.

1|1|Updated Feb 28, 2026

Search Tags:#workflow #task management #archive #change management #openspec #specification sync

Ready to run

npx skills add https://github.com/kevintsengtw/dotnet-testing-agent-orchestration --skill openspec-archive-change-kevintsengtw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/kevintsengtw/dotnet-testing-agent-orchestration/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/kevintsengtw/dotnet-testing-agent-orchestration --skill openspec-archive-change-kevintsengtw

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

Automated Archiving: Moves completed changes to an archive directory with a timestamped name.
Status Checks: Verifies artifact and task completion before archiving, providing warnings for incomplete items.
Delta Spec Sync: Assesses and optionally syncs delta specifications with main specifications before archiving.
Use Case: After successfully implementing a new feature and testing it, use this Skill to archive the associated change, ensuring all related artifacts and tasks are accounted for and specifications are up-to-date.

Quick Start

Use the openspec-archive-change skill to archive the change named 'user-authentication-flow'.

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 a workflow and ensure all tasks are done?▼

To archive completed changes, the process verifies artifact and task completion statuses before moving the change directory to a timestamped archive location. It also optionally syncs delta specifications with main specifications to ensure your project history stays organized.

What happens to incomplete tasks or artifacts when archiving a change?▼

When archiving a change, the system checks artifact and task statuses and provides warnings for any incomplete items. This ensures you are aware of pending work before the change directory is moved to the archive location.

Do I need the openspec CLI to sync delta specifications during change management?▼

Yes, syncing delta specifications with main specifications requires the openspec CLI. The CLI is used to assess the delta spec sync state and perform the sync operations before the change is archived.

Can I automatically move completed change directories to an archive location?▼

Yes, automated archiving moves completed change directories to an archive location with a timestamped name. This helps maintain a clean and organized project history after a feature is implemented and tested.

When should I sync delta specifications with main specifications in change management?▼

You should sync delta specifications with main specifications before archiving a completed change. The archiving process assesses the sync state and optionally applies the sync to ensure all specifications are up-to-date in the project history.