openspec-archive-change

Validate OpenSpec workflow artifacts and tasks before archiving completed changes.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/evandrodevbr/GeminiNexus --skill openspec-archive-change-evandrodevbr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/evandrodevbr/GeminiNexus/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/evandrodevbr/GeminiNexus --skill openspec-archive-change-evandrodevbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps finalize completed OpenSpec changes by validating workflow status, checking unfinished work, and archiving changes safely without losing required metadata.

Core Features & Use Cases

  • Completion Validation: Checks artifact and task completion states before archiving a change.
  • Safe Archiving Workflow: Reviews specification synchronization status and moves completed changes into dated archive locations.
  • Use Case: Use this Skill after implementing a feature to verify the OpenSpec change is ready and archive it with a clear completion summary.

Quick Start

Use the openspec-archive-change skill to archive the completed change named feature-update after verifying its status.

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 workflow metadata?

To safely archive OpenSpec changes, validate artifact completion, task statuses, and specification synchronization state before moving change directories into dated archive locations, ensuring workflow metadata is preserved and a completion summary is generated.

What does specification synchronization status check before archiving a change?

Specification synchronization status checks whether your OpenSpec implementation proposals and artifacts are fully aligned and completed before the change is approved for archiving, preventing unfinished work from being moved to the archive.

How do I validate OpenSpec task completion before moving change directories?

You validate OpenSpec task completion by executing structured status checks that verify all artifacts and tasks are finished, ensuring the workflow integrity is intact before the change is archived with a generated summary.

Do I need the openspec command execution environment to archive workflow changes?

Yes, archiving OpenSpec workflow changes requires the openspec command execution environment to run structured status checks, validate artifacts, and safely move completed change directories into dated archive locations.

What is the best way to finalize completed implementation proposals in change management?

The best way to finalize implementation proposals is to validate workflow status, check for unfinished work, verify specification synchronization, and archive the change safely into dated locations with a clear completion summary.

Why does archiving a change fail when artifact validation finds unfinished tasks?

Archiving a change fails during artifact validation because the OpenSpec workflow requires all tasks and specification synchronization states to be fully completed, preventing incomplete changes from being moved into the archive.