openspec-archive-change

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

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/optioni/dungeons-and-dragons --skill openspec-archive-change-optioni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/optioni/dungeons-and-dragons/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/optioni/dungeons-and-dragons --skill openspec-archive-change-optioni

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill allows users to archive completed changes in the experimental workflow, ensuring that changes are finalized and stored securely.

Core Features & Use Cases

  • Archive Completed Changes: Finalize and archive changes after implementation is complete.
  • User Selection: Optionally specify a change name or let the Skill infer from context.
  • Status Checks: Verify artifact and task completion before archiving.
  • Spec Sync Assessment: Check and sync delta specs before archiving if needed.
  • Archive Summary: Provide a summary of the archiving process, including schema, location, and warnings.

Quick Start

Archive the completed change named 'featureX'.

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

You can finalize and archive completed changes by selecting a specific change name or letting the Skill infer it from context. The process verifies artifact completion, syncs delta specs, and outputs an archive summary with schema and location details.

What is the process to finalize and store completed change specifications?

The process checks artifact and task completion status, synchronizes delta specs, and archives the finalized changes securely. It requires user input for change selection and confirmation before generating an archive process summary.

Do I need the openspec CLI to archive completed changes?

Yes, the openspec CLI is a required dependency for this Skill. It handles the underlying commands needed to check completion status, synchronize delta specs, and execute the archiving process for your changes.

Can I specify a change name manually when archiving workflow changes?

Yes, you can optionally specify a change name manually for archiving. If you do not provide a name, the Skill will infer the appropriate change from the current context to proceed with finalization.

What happens if artifacts or tasks are not complete before archiving?

Before archiving, the Skill performs status checks to verify all artifacts and tasks are complete. This ensures incomplete changes are not finalized and confirms delta specs are synchronized before proceeding.

Why does the archiving process sync delta specs?

Syncing delta specs ensures the archived change records accurately reflect all implementation modifications. This assessment checks and updates specifications before finalization, maintaining consistency across the stored workflow artifacts.