openspec-archive-change

Archive completed change directories with date-stamped naming conventions.

43|24|Updated Jul 3, 2018

Search Tags:#workflow #archive #change management #openspec #task completion #specification sync

Ready to run

npx skills add https://github.com/tsedio/tsed-cli --skill openspec-archive-change-tsedio

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-sync-specs, and 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 change directories to a designated archive location.
Status Checks: Verifies artifact and task completion before archiving.
Delta Spec Sync: Assesses and optionally syncs delta specifications with main specifications.
Use Case: After implementing a new feature and testing it thoroughly, use this Skill to archive the associated change, ensuring all related artifacts and tasks are accounted for and specifications are up-to-date.

Quick Start

Use the openspec-archive-change skill to archive the change named 'new-user-authentication'.

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

Archiving completed changes involves moving change directories to a designated archive location with date-stamped naming conventions. This Skill verifies artifact and task completion before relocation.

What does change management archiving verify before moving files?▼

Before archiving, the process verifies that all artifacts and tasks associated with the change are complete. It also assesses delta specifications to ensure project documentation is current.

Do I need the openspec CLI to sync delta specifications during task completion?▼

Yes, you need the openspec CLI to perform status checks and optionally synchronize delta specifications with main specifications when archiving a completed change.

Can I sync delta specifications with main specifications when archiving?▼

Yes, you can optionally sync delta specifications with main specifications during archiving. The process assesses deltas and uses the openspec CLI to synchronize them.

Why does change archiving fail if artifacts are incomplete?▼

Change archiving requires all artifacts and tasks to be complete before moving directories. This status check prevents archiving unfinished work and maintains project history integrity.

What is the best way to organize completed change directories?▼

The best way to organize completed change directories is moving them to a designated archive location with date-stamped naming conventions, which this Skill automates.