skills.rest
thalesraymond
thalesraymondCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed changes after verifying artifacts and tasks with openspec CLI.

1|Updated Mar 7, 2026
Search Tags:#workflow#task management#archive#change management#openspec#spec sync
One-click install
npx skills add https://github.com/thalesraymond/release-gamification --skill openspec-archive-change-thalesraymond
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/thalesraymond/release-gamification/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/thalesraymond/release-gamification --skill openspec-archive-change-thalesraymond

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.
  • Status Checks: Verifies artifact and task completion before archiving.
  • Spec Syncing: Assesses and optionally syncs delta specs with main specs.
  • Use Case: After successfully implementing a new feature and testing all associated artifacts and tasks, you can use this Skill to archive the change, marking it as complete and moving it out of the active development area.

Quick Start

Use the openspec-archive-change skill to archive the change named 'feature-x'.

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 workflow changes with date-stamped directories?▼

To archive completed workflow changes, this Skill verifies artifact and task completion, assesses delta spec synchronization status, and moves the change directory to an archive location with a date-stamped name to finalize project history.

What happens if delta specs are not synchronized with main specs during change archiving?▼

During change archiving, if delta specs are not synchronized with main specs, the Skill assesses the synchronization status and prompts you to sync them before moving the change directory to the archive location.

Do I need the openspec CLI to archive completed changes and verify task completion?▼

Yes, you need the openspec CLI installed to archive completed changes, as the Skill requires it for performing status checks and handling potential delta spec synchronization before moving the directory.

How does change management workflow verify artifact and task completion before archiving?▼

Change management workflow verifies artifact and task completion by running status checks through the openspec CLI, ensuring all related artifacts and tasks are successfully completed before allowing the change directory to move to the archive.

Can I move incomplete change tasks to the archive location in the experimental workflow?▼

No, you cannot move incomplete change tasks to the archive location because the Skill enforces artifact and task completion verification, blocking the archiving process until all associated tasks are marked complete.

Related Skills

Explore More Software Engineering Skills→
Pony-UnicornPony-Unicorn
7

openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

Community
Advanced
tsediotsedio
43

openspec-archive-change

Archive completed change directories with date-stamped naming conventions.

Official
Advanced
Myriad-DreaminMyriad-Dreamin
3.5k

openspec-archive-change

Archive completed changes in the experimental workflow using the openspec CLI.

Community
Intermediate
brainsnorkelbrainsnorkel

openspec-archive-change

Archive completed changes in the experimental workflow via the openspec CLI.

Community
Advanced