openspec-archive-change

Archive completed openspec experimental changes to dated directories with validation.

3|1|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/accidental-hedge-fund/agent-pipeline --skill openspec-archive-change-accidental-hedge-fund
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/accidental-hedge-fund/agent-pipeline/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/accidental-hedge-fund/agent-pipeline --skill openspec-archive-change-accidental-hedge-fund

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking and organizing completed experimental workflow changes leads to cluttered project directories and risk of losing work if changes are not properly archived after implementation.

Core Features & Use Cases

  • Completion Validation: Automatically checks that all change artifacts and tasks are marked complete before allowing archival, preventing unfinished work from being moved.
  • Delta Spec Sync: Assesses and syncs any delta specs to main project specs during archival to keep documentation up to date.
  • Use Case: After finishing an openspec experimental change for a new feature, use this skill to safely move the change folder to a dated archive directory with all validations and syncs handled automatically.

Quick Start

Use the openspec-archive-change skill to archive the completed experimental change you just finished implementing.

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 openspec experimental changes without losing track of tasks?

To archive completed openspec experimental changes safely, this skill validates that all change artifacts and tasks are marked complete before moving the change folder to a dated archive directory.

What is the best way to sync delta specs to main project specs during change archival?

Syncing delta specs to main project specs during change archival involves assessing the experimental changes and automatically updating the main documentation to keep project specs current without manual file management.

How does completion validation work for openspec change archival?

Completion validation for openspec change archival automatically checks that all associated change artifacts and tasks are marked complete, preventing unfinished work from being moved to the archive directory.

Can I move unfinished openspec experimental changes to the archive directory?

No, you cannot move unfinished openspec experimental changes because the archival process requires completion verification for all change artifacts and tasks to prevent losing work.

Do I need to manually manage dated directories when archiving openspec changes?

No, you do not need to manually manage dated directories because the archival process automatically handles safe file movement to a dated archive directory for your completed experimental workflow changes.