openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: Augentic

Archive completed OpenSpec changes with verified artifacts and delta spec sync assessment.

Updated Aug 27, 2026

Search Tags:#workflow #version control #task management #archive #change management #openspec

Ready to run

npx skills add https://github.com/augentic/vectis --skill openspec-archive-change-augentic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/augentic/vectis/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/augentic/vectis --skill openspec-archive-change-augentic

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the experimental workflow by providing a clear process to archive completed changes, ensuring a clean and organized project history.

Core Features & Use Cases

Automated Archiving: Moves completed changes to an archive directory with a date-stamped name.
Status Verification: Checks artifact and task completion before archiving, warning the user of any incomplete items.
Delta Spec Sync Assessment: Analyzes and reports on the synchronization state of delta specs with main specs.
Use Case: After successfully implementing a new feature using the OpenSpec workflow, use this Skill to formally archive the change, ensuring all related artifacts and tasks are accounted for and the project state is clean.

Quick Start

Use the openspec-archive-change skill to archive the change named 'my-new-feature'.

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 a version control workflow?▼

Archiving completed changes involves verifying all artifacts and tasks are complete, assessing delta spec synchronization, and moving the change directory to a date-stamped archive location to maintain a clean project history.

What happens if I try to archive a change with incomplete tasks?▼

When archiving a change with incomplete tasks, the system performs status verification on artifacts and tasks, warning you of any incomplete items to prevent losing track of unfinished work.

How does delta spec synchronization assessment work when archiving changes?▼

Delta spec synchronization assessment analyzes and reports on the synchronization state of delta specs with main specs before archiving, ensuring your experimental workflow maintains consistency across version-controlled specifications.

When should I archive a completed change in my task management workflow?▼

You should archive a completed change after successfully implementing a new feature, ensuring all related artifacts and tasks are accounted for and your project state remains clean and organized.

Do I need any dependencies to archive changes in the OpenSpec workflow?▼

No dependencies are required to archive changes in the OpenSpec workflow, as the skill operates independently using internal scripts and references to handle verification and directory relocation.

What is the best way to organize completed feature changes in version control?▼

The best way to organize completed feature changes is to move them to a date-stamped archive directory after verifying all tasks and artifacts, ensuring a clean and organized project history.