openspec-archive-change

Archives completed experimental workflow changes using the openspec CLI.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/DihDyyy/login_app --skill openspec-archive-change-dihdyyy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/DihDyyy/login_app/tree/main/.amazonq/skills/openspec-archive-change
Command: npx skills add https://github.com/DihDyyy/login_app --skill openspec-archive-change-dihdyyy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill allows you to archive completed changes in the experimental workflow, ensuring that changes are properly stored and organized after implementation.

Core Features & Use Cases

  • Archive Completed Changes: Finalize and archive changes once they are implemented and complete.
  • Artifact Completion Check: Confirm that all artifacts associated with the change are complete before archiving.
  • Task Completion Check: Verify that all necessary tasks are completed before archiving.
  • Spec Sync Assessment: Determine if delta specs need to be synced before archiving.
  • Archive Creation: Create an archive directory and move the change to it, generating a unique target name.

Quick Start

Use the openspec-archive-change skill to archive the completed change named 'my_change'.

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

You can archive completed changes by selecting a specific change, verifying all associated artifacts and tasks are complete, and executing the archive operation through the openspec CLI.

What is the process for finalizing completed changes in an experimental workflow?

Finalizing completed changes involves confirming artifact and task completion, evaluating delta spec sync status, and creating an archive directory to properly store the implemented change.

Do I need the openspec CLI to archive completed changes?

Yes, the openspec CLI is a required dependency for archiving completed changes, as the Skill relies on it to perform the archive operation, check completion, and assess spec synchronization.

How does the archive creation mechanism work for completed changes?

The archive creation mechanism works by generating a unique target name for an archive directory and moving the completed change into it, confirming that all artifacts and tasks are finished beforehand.