source-command-opsx-archive

Archive completed changes in an experimental workflow with delta spec sync.

9|3|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Kahtaf/OpenCandle --skill source-command-opsx-archive-kahtaf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-opsx-archive
Source: https://github.com/Kahtaf/OpenCandle/tree/main/.agents/skills/source-command-opsx-archive
Command: npx skills add https://github.com/Kahtaf/OpenCandle --skill source-command-opsx-archive-kahtaf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the archiving of completed changes in the experimental workflow, streamlining the process and ensuring data integrity.

Core Features & Use Cases

  • Archive Completed Changes: Automatically archive changes once they are completed.
  • User Confirmation: Prompt the user for confirmation if there are incomplete artifacts or tasks.
  • Delta Spec Sync: Offer to sync delta specs before archiving.
  • Summary Display: Provide a summary of the archive process, including the schema used, archive location, and spec sync status.
  • Use Case: Ideal for teams using an experimental workflow where changes need to be archived after completion to maintain a clean and organized workflow.

Quick Start

Run the source-command-opsx-archive skill to archive a completed change in the experimental workflow.

Frequently Asked Questions about source-command-opsx-archive

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

FAQPage Schema
How do I automate workflow archiving for completed changes in an experimental environment?

Automated workflow archiving checks artifact and task completion, prompts for confirmation on incomplete items, syncs delta specs, and archives the change with a process summary. This streamlines workflow automation by ensuring data integrity during the archiving process.

What happens if some artifacts or tasks are incomplete when I try to archive a change?

If artifacts or tasks are incomplete during change archiving, the system prompts the user for confirmation before proceeding. This change tracking mechanism ensures you do not accidentally archive unfinished work in your experimental workflow environment.

Does the archive process sync delta specs before finalizing the change?

Yes, the archive process offers to sync delta specs before finalizing the completed change. This specification management step ensures all delta specifications are up to date in the archive location before the workflow archiving completes.

What information is included in the summary after archiving an experimental workflow change?

The archive summary displays the schema used, the archive location, and the spec sync status. This change tracking output provides full visibility into the automated archiving process for your completed experimental workflow changes.

Do I need specific tools to run change archiving in the experimental workflow?

Yes, change archiving requires access to the experimental workflow environment and relevant tools for change listing, status checking, and archiving. These dependencies are necessary to verify completion and execute the workflow automation properly.