openspec-archive-change

Archive completed changes after verifying artifact and task completion status.

133|23|Updated Mar 23, 2020

Search Tags:#workflow #version control #archive #change management #spec sync #openspec cli

Ready to run

npx skills add https://github.com/aehrc/pathling --skill openspec-archive-change-aehrc

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of archiving completed changes within an experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

Automated Archiving: Moves completed changes to a designated archive location.
Status Verification: Checks artifact and task completion before archiving.
Spec Synchronization: Optionally syncs delta specifications with main specifications.
Use Case: After successfully implementing a new feature and testing all associated artifacts and tasks, use this Skill to archive the change, maintaining a clear record of completed work.

Quick Start

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

Frequently Asked Questions about openspec-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the best way to archive completed workflow changes and verify task status?▼

The best way to archive completed workflow changes is to use an automated archiving tool that verifies task and artifact completion status before moving the change directory to a designated archive location.

How do I synchronize delta specifications with main specifications before archiving a change?▼

You can synchronize delta specifications with main specifications by using a spec sync tool that optionally integrates this step before archiving a completed change, ensuring your main project records remain updated.

Do I need the openspec CLI to verify artifact completion before archiving?▼

Yes, you need the openspec CLI to verify artifact and task completion status, as it is required to perform status checks and list changes before the archiving process executes.

When should I archive a change in an experimental workflow?▼

You should archive a change in an experimental workflow only after successfully implementing a new feature and verifying that all associated artifacts and tasks are completed and tested.

Can I use automated archiving to maintain a clean project history for completed features?▼

Yes, automated archiving maintains a clean project history by moving completed change directories to a designated archive location, streamlining the process and ensuring an organized record of completed work.