openspec-archive-change

Archive completed experimental changes after verifying artifact and task status.

Updated May 5, 2022
One-click install
npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-archive-change-blackbelttechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/BlackBeltTechnology/judo-runtime-core/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-archive-change-blackbelttechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you finalize and archive completed changes within the experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

  • Workflow Finalization: Safely archive completed experimental changes.
  • Status Checks: Verifies artifact and task completion before archiving.
  • Spec Synchronization: Optionally syncs delta specs with main specs before archiving.
  • Use Case: After implementing a new feature and testing it, use this skill to archive the change, ensuring all related artifacts and tasks are accounted for and specs are up-to-date.

Quick Start

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

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 experimental changes in a software workflow?

Archiving experimental changes involves verifying artifact and task completion status, optionally synchronizing delta specifications with main specs, and moving the change to an archive directory to finalize the workflow.

What is the process to sync delta specifications with main specs before archiving?

Spec synchronization updates main specifications with delta changes before moving the change to an archive directory, ensuring project documentation remains current and accurately reflects the completed experimental work.

Do I need the openspec CLI to verify task completion before archiving changes?

Yes, archiving changes requires the openspec CLI to perform status checks, verify artifact and task completion, and list available changes before moving them to the archive directory.

What happens if artifact and task completion checks fail during change archiving?

The archiving process verifies artifact and task completion status before moving changes to an archive directory, preventing incomplete experimental changes from being finalized in the project history.

When should I archive experimental changes instead of keeping them active?

Archive experimental changes after implementing a new feature and testing it, ensuring all related artifacts and tasks are accounted for and specs are up-to-date to maintain a clean project history.

Does openspec-archive-change support synchronizing specifications during the archiving process?

Yes, openspec-archive-change supports optional synchronization of delta specifications with main specifications before moving the completed change to an archive directory, ensuring documentation consistency.