skills.rest
stevemac007
stevemac007COMMUNITY
Explore all skills by this author →
Website𝕏@stevemac007GitHub

openspec-archive-change

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

Updated May 3, 2026
Search Tags:#workflow#specification#CLI#archive#change management
One-click install
npx skills add https://github.com/stevemac007/subtracker-app --skill openspec-archive-change-stevemac007
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/stevemac007/subtracker-app/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/stevemac007/subtracker-app --skill openspec-archive-change-stevemac007

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of archiving completed changes in the experimental workflow, ensuring that changes are securely stored and easily accessible for future reference.

Core Features & Use Cases

  • Archive Completed Changes: Securely archive changes after implementation is complete.
  • Change Selection: Prompt for change selection if not provided, ensuring user choice.
  • Artifact and Task Completion Checks: Verify artifact and task completion before archiving.
  • Spec Sync Assessment: Assess delta spec sync state and prompt for sync if needed.
  • Archive Execution: Perform the archive operation with detailed summary.
  • Use Case: After a feature is implemented and tested, use this Skill to archive the change, ensuring all related data is preserved.

Quick Start

Archive the completed change 'featureX' in the experimental workflow.

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?▼

To archive completed changes, you verify artifact and task completion, assess delta spec sync state, and execute the archive operation to securely store the finalized change data.

What is the best way to finalize and archive a completed software specification?▼

Finalizing a software specification requires verifying artifact completion, checking spec sync state, and executing an archive operation to ensure data integrity and preserve the change history.

Do I need the openspec CLI to manage change archiving?▼

Yes, the openspec CLI is required as a dependency to manage change archiving, assess delta spec synchronization, and execute the final archive operation securely.

Can I archive a change if artifact and task completion checks have not passed?▼

No, artifact and task completion checks must pass before archiving. The workflow verifies completion and prompts for spec sync to ensure data integrity before executing the archive.

How does spec sync assessment work before archiving a change?▼

Spec sync assessment evaluates the delta spec synchronization state before archiving, prompting the user to sync if needed to prevent data inconsistencies in the archived change.

Why does the archive process prompt for change selection?▼

The archive process prompts for change selection to ensure user choice when a specific change is not explicitly provided, guaranteeing the correct completed feature is securely archived.

Related Skills

Explore More Software Engineering Skills→
rock-hurock-hu

openspec-archive-change

Archive completed openspec changes into dated paths after validating artifacts and tasks.

Community
Advanced
sundaiclawsundaiclaw
7

openspec-archive-change

Archive completed OpenSpec changes with artifact and delta-spec checks.

Community
Advanced
lihaizhonglihaizhong

openspec-archive-change

Finalize and archive completed changes in an experimental workflow.

Community
Advanced
deicerdeicer

openspec-archive-change

Archive completed changes after verifying artifacts, tasks, and delta spec sync.

Community
Advanced