openspec-archive-change

Archive completed openspec changes after validating artifacts, tasks, and delta spec sync.

Updated Jan 18, 2026

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

Ready to run

npx skills add https://github.com/tungnguyen10/iuh_department --skill openspec-archive-change-tungnguyen10

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/tungnguyen10/iuh_department/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/tungnguyen10/iuh_department --skill openspec-archive-change-tungnguyen10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually archiving openspec changes risks storing incomplete work, missing spec syncs, and disorganized change records that are hard to track later.

Core Features & Use Cases

Pre-archive validation: Checks artifact and task completion status to prevent incomplete work from being archived.
Delta spec sync assessment: Evaluates if change-specific specs need to be synced to main specs before archiving, with clear prompts for user choice.
Dated archive organization: Automatically moves completed changes to a dated archive directory for consistent, traceable record-keeping. Use case: For development teams using the openspec experimental workflow, use this skill to safely archive finished feature changes after confirming all work is complete and specifications are up to date.

Quick Start

Use the openspec-archive-change skill to archive the completed 'payment-gateway-integration' change after verifying all required artifacts and tasks are finished.

Frequently Asked Questions about openspec-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely archive completed openspec changes without losing track of unfinished tasks?▼

To safely archive openspec changes, use a pre-archive validation process that checks artifact completion and task status, preventing incomplete work from being moved to the dated archive directory.

What is the best way to sync delta specs to main specs before archiving a feature change?▼

The best way to sync delta specs before archiving is to evaluate if change-specific specs require synchronization with main specs, prompting the user to choose whether to sync prior to final archival.

Does openspec archive validation check if all required artifacts are finished?▼

Yes, openspec archive validation checks artifact completion status and task tracking records to enforce guardrails against incomplete work and ensure organized, traceable change record-keeping.

How do I organize archived openspec workflow changes for consistent traceability?▼

You can organize archived openspec workflow changes by automatically moving completed feature changes into a dated archive directory, ensuring consistent and traceable record-keeping for development teams.

What happens if I try to archive an openspec change with unsynced project specifications?▼

If you attempt to archive an openspec change with unsynced specifications, the delta spec sync assessment triggers clear prompts for your choice, ensuring project specifications are reviewed before archival.