openspec-archive-change

Archive completed openspec workflow changes with validation and metadata preservation.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/futuretea/x-project --skill openspec-archive-change-futuretea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/futuretea/x-project/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/futuretea/x-project --skill openspec-archive-change-futuretea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental openspec workflow to ensure changes are finalized and properly stored.

Core Features & Use Cases

  • Interactive change selection when a name is provided or omitted, ensuring only active changes are chosen.
  • Validation of artifacts and tasks across the change lifecycle, including delta-spec sync assessment.
  • Safe archiving with metadata preservation, archive directory creation, and a clear, auditable summary on completion.

Quick Start

Provide the change name to archive and follow the guided steps to validate and move the change into the archive.

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 the openspec workflow?

To archive completed openspec changes, provide the change name to trigger interactive selection, validate artifacts and tasks, assess delta-spec sync, and safely relocate the change with preserved metadata into an archive directory.

What is delta-spec synchronization validation for workflow archiving?

Delta-spec synchronization validation checks if the delta-spec is properly synced before archiving, ensuring completed changes are finalized, metadata is preserved, and artifacts are safely relocated into the archive.

Can I archive an openspec change without providing a specific name?

Yes, when a change name is omitted, interactive change selection is triggered, allowing you to choose which active openspec changes to validate and safely archive from the available options.

How to validate openspec artifacts and tasks before archiving?

Validating openspec artifacts and tasks before archiving involves assessing delta-spec sync, enforcing guardrails across the change lifecycle, and ensuring all components are finalized before safe relocation into the archive.

Does the openspec archive process generate an audit summary?

Yes, the openspec archive process outputs a clear, auditable success report upon completion, summarizing the validated artifacts, relocated files, and preserved metadata suitable for operational audits.

What are the limitations of archiving openspec workflow changes?

Limitations include being constrained to the experimental openspec workflow, requiring completed artifact and task validation, and enforcing strict guardrails that prevent archiving changes with incomplete delta-spec synchronization.