openspec-archive-change

Finalize and archive completed changes using the openspec CLI.

Updated May 14, 2026
One-click install
npx skills add https://github.com/bruinalphainvestment/bai-website --skill openspec-archive-change-bruinalphainvestment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/bruinalphainvestment/bai-website/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/bruinalphainvestment/bai-website --skill openspec-archive-change-bruinalphainvestment

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users finalize and archive completed changes in the experimental workflow, ensuring changes are properly documented and stored.

Core Features & Use Cases

  • Archive Completed Changes: Finalize and archive changes after implementation is complete.
  • Change Selection: Prompt for change selection if not provided.
  • Completion Status Check: Check artifact and task completion status.
  • Spec Sync Assessment: Assess delta spec sync state and prompt for sync.
  • Archive Execution: Perform the actual archive process.
  • Summary Display: Provide a summary of the archive completion.

Quick Start

Use the openspec-archive-change skill to archive a completed change in the experimental workflow. Optionally specify a change name or let the skill infer it from context.

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 an experimental workflow?

To archive completed changes in an experimental workflow, you can finalize and store them by assessing delta spec sync state and executing the archiving process to ensure proper documentation and storage.

What is the process for change tracking and specification sync before archiving?

Specification sync before archiving involves assessing the delta spec sync state and prompting the user to synchronize, ensuring completed tasks and artifacts align with change tracking records.

Do I need the openspec CLI to finalize and archive changes?

Yes, you need the openspec CLI installed as a dependency, because the Skill requires it specifically for executing change management operations and checking completion status.

How does change management handle completion status checks for archiving?

Change management handles completion status checks by verifying that all required artifacts and tasks are finished before allowing the archiving actions to proceed in the workflow.

What happens if a change name is not specified during the archive process?

If a change name is not specified during the archive process, the Skill handles user interaction by prompting for change selection or attempting to infer the correct change from the current context.