openspec-archive-change

Archives completed experimental workflow changes after validating tasks and spec sync status with openspec CLI.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/gokhantaskan/fastback --skill openspec-archive-change-gokhantaskan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/gokhantaskan/fastback/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/gokhantaskan/fastback --skill openspec-archive-change-gokhantaskan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill facilitates the archiving of completed changes in the experimental workflow, ensuring a systematic process for finalizing and storing implemented changes.

Core Features & Use Cases

  • Change Archival: Systematically archive changes after implementation to maintain a history of experimental workflow activities.
  • User Prompting: Informs the user to select a change for archiving and confirms completion status.
  • Spec Sync Assessment: Assesses delta spec sync state before archiving to ensure consistency.

Quick Start

Use the openspec-archive-change skill to archive a completed change named 'feature-1'.

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 a completed change in an experimental workflow?

To archive a completed change in an experimental workflow, the system prompts you to select the change, validates artifact and task completion, and checks delta spec sync status before finalizing the archival.

What is delta spec sync status and why is it checked before archiving?

Delta spec sync status is a consistency check ensuring your experimental changes align with existing specifications. It is assessed before archiving to guarantee that only fully synchronized and completed changes are stored in the workflow history.

Do I need the openspec CLI to finalize and archive changes?

Yes, you need the openspec CLI installed to finalize and archive changes. The archival process requires this CLI tool to properly assess the schema and validate the consistency of the experimental workflow before storing the completed change.

How does change archival validate task completion before storing history?

Change archival validates task completion by prompting the user to select a finalized change and then verifying that all associated artifacts and tasks are completed. This ensures only fully implemented changes are archived into the workflow history.

Can I use this archival process for incomplete experimental workflow changes?

No, this archival process is designed exclusively for completed changes. It validates artifact and task completion while checking delta spec sync status, preventing incomplete experimental workflow changes from being finalized and stored.