openspec-archive-change

Archives a completed experimental change after verifying artifacts, tasks, and delta specs.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/dungsnowaxe/prometheus-red-team-bot --skill openspec-archive-change-dungsnowaxe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/dungsnowaxe/prometheus-red-team-bot/tree/main/.windsurf/skills/openspec-archive-change
Command: npx skills add https://github.com/dungsnowaxe/prometheus-red-team-bot --skill openspec-archive-change-dungsnowaxe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed experimental changes within a 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.
  • Spec Synchronization: Assesses and optionally syncs delta specs with main specs.
  • Use Case: After successfully implementing and testing a new feature defined by an experimental change, use this Skill to archive it, ensuring all related artifacts and tasks are verified and specs are up-to-date.

Quick Start

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

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 experimental changes in a version control workflow?

To archive experimental changes, the skill verifies artifact and task completion, assesses delta spec synchronization, and moves the change to a date-stamped archive directory. It prompts for confirmation if incomplete artifacts or tasks are found during the process.

What happens if I try to archive an experimental change with incomplete tasks?

When archiving an experimental change with incomplete tasks, the workflow prompts you for confirmation before proceeding. This status verification ensures you do not accidentally archive unfinished artifacts or uncompleted tasks into the project history.

Can I synchronize delta specs with main specs before moving changes to the archive?

Yes, you can synchronize delta specs with main specs before archiving. The skill assesses delta spec synchronization and offers options to sync them, ensuring your main specifications remain up-to-date when the experimental change is archived.

What is spec synchronization and when do I need it for archiving experimental changes?

Spec synchronization aligns delta specs generated during experimental changes with your main project specifications. You need it before archiving to ensure the archived workflow reflects a clean, organized project history without specification drift.

Does the archiving process require any external dependencies or scripts?

No external dependencies are required for the archiving process. The skill operates using internal scripts to verify task completion, sync delta specs, and generate the date-stamped archive directory name automatically within your workflow.