skills.rest
emergent-company
emergent-companyOFFICIAL
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

1|Updated Feb 6, 2026
Search Tags:#workflow#archive#change management#openspec#task completion#spec synchronization
One-click install
npx skills add https://github.com/emergent-company/emergent.memory --skill openspec-archive-change-emergent-company
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/emergent-company/emergent.memory/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/emergent-company/emergent.memory --skill openspec-archive-change-emergent-company

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the finalization of experimental workflows by archiving completed changes, ensuring a clean and organized project history.

Core Features & Use Cases

  • Automated Archiving: Moves completed change directories to a designated archive location.
  • Status Verification: Checks artifact and task completion before archiving, providing warnings for incomplete items.
  • Delta Spec Sync: Assesses and optionally syncs delta specifications with main specifications.
  • Use Case: After successfully implementing a new feature and testing all associated artifacts and tasks, use this Skill to formally archive the 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, this skill verifies artifact and task completion status, assesses delta spec synchronization, and moves the change directory to a designated archive location. It requires the openspec CLI for status checks and potential synchronization.

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

When archiving a change with incomplete items, the skill performs status verification and provides warnings for incomplete artifacts or tasks. It assesses delta spec synchronization before moving the change directory to ensure project history remains organized.

How does delta spec synchronization work during change archiving?▼

Delta spec synchronization assesses experimental workflow changes against main specifications before archiving. The skill optionally syncs these delta specifications using the openspec CLI, ensuring completed changes align with the main project specs when moved to the archive location.

Do I need the openspec CLI to use automated change archiving?▼

Yes, the openspec CLI is required for automated change archiving. The skill depends on it to verify artifact and task completion status and to assess or synchronize delta specifications before moving the change directory to the archive.

When should I archive a change directory in change management?▼

You should archive a change directory after successfully implementing a new feature and testing all associated artifacts and tasks. This finalizes the experimental workflow, marks the change as complete, and maintains a clean, organized project history.

Related Skills

Explore More Software Engineering Skills→
rock-hurock-hu

openspec-archive-change

Archive completed openspec changes into dated paths after validating artifacts and tasks.

Community
Advanced
rick2047rick2047

openspec-sync-specs

Merge delta specs into main specs with ADDED/MODIFIED/REMOVED/RENAMED guidance.

Community
Advanced
ywh0606ywh0606

opsx-verify

Verify OpenSpec changes for completion and readiness before archiving.

Community
Intermediate
brandon-setegnbrandon-setegn

openspec-archive-change

Validate task completion and sync specs before archiving OpenSpec changes.

Community
Advanced