openspec-archive-change

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

Finalizes and archives approved changes in the OpenSpec CLI workflow.

4|Updated Jan 24, 2025

Search Tags:#workflow #archive #CLI tool #change management #change tracking

Ready to run

npx skills add https://github.com/rdkcentral/tr69hostif --skill openspec-archive-change-rdkcentral

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Streamlines the process of archiving completed changes in the experimental workflow, ensuring changes are finalized and documented appropriately.

Core Features & Use Cases

Archive Change: Permanently store completed changes after finalization.
Change Selection: Prompt for selection if a change name is not provided, allowing users to choose from available options.
Status Checking: Verify the completion status of artifacts and tasks before archiving.
Spec Syncing: Offers to sync delta specs before archiving, providing a choice for users.
Summary Display: Show a detailed summary upon successful archiving, including the schema used and archive location.

Quick Start

Use the openspec-archive-change skill to archive a completed change in the experimental workflow.

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 using openspec?▼

To archive completed changes, you use the openspec CLI to finalize and permanently store them. The process checks artifact and task completion status, offers spec syncing, and then archives the selected change.

What is the process for finalizing and tracking change management status before archiving?▼

Change tracking finalization involves checking the completion status of all related artifacts and tasks. The workflow verifies these elements are complete, offers to sync delta specs, and then permanently archives the change.

Do I need the openspec CLI installed to archive changes in the experimental workflow?▼

Yes, the openspec CLI is required to archive changes in the experimental workflow. The archiving process relies on this CLI tool to execute the underlying change management operations and ensure proper finalization.

Can I sync delta specs before archiving a change?▼

Yes, you can sync delta specs before archiving a change. The workflow explicitly offers a choice to sync delta specs during the finalization process, ensuring all modifications are updated before permanent archival.

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

If you try to archive a change with incomplete tasks, the workflow checks artifact and task completion status beforehand. This verification prevents archiving incomplete changes, ensuring only fully finalized modifications are permanently stored.

How do I select a specific change to archive if I have multiple active workflows?▼

To select a specific change to archive among multiple active workflows, the system prompts you with available options. This change selection prompt appears when a change name is not provided, allowing you to choose the correct one.