openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: YangYuS8

Archive multiple completed OpenSpec changes with status checks and conflict resolution.

Updated Mar 7, 2026

Search Tags:#workflow #audit #archive #batch #openspec #changes

Ready to run

npx skills add https://github.com/YangYuS8/blog --skill openspec-bulk-archive-change-yangyus8

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/YangYuS8/blog/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/YangYuS8/blog --skill openspec-bulk-archive-change-yangyus8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving multiple completed changes in a single operation to streamline change lifecycle and keep active work focused.

Core Features & Use Cases

Batch archiving of multiple completed changes from the OpenSpec project, including status checks and task counts.
Conflict detection and guided resolution using the incremental specs to maintain consistency across changes.
Auditable archiving with date-stamped directories (archive/YYYY-MM-DD-<name>) and preserved specs for traceability.

Quick Start

Select the completed changes and run the bulk archive operation to move them to the archive directory with an audit record.

Frequently Asked Questions about openspec-bulk-archive-change

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

FAQPage Schema

How do I batch archive completed changes in OpenSpec to streamline the change lifecycle?▼

Batch archiving completed changes in OpenSpec lets you move multiple finalized entries into a date-stamped directory in a single operation, reducing manual steps and keeping active work focused. The process includes status validation and task counting.

What happens when archiving multiple changes causes specification conflicts?▼

When bulk archiving detects specification conflicts across multiple changes, it applies conflict-aware specification reconciliation using incremental specs to maintain consistency. The workflow guides users through resolution to ensure safe archiving without breaking traceability.

Can I use a single confirmation workflow to archive multiple OpenSpec changes safely?▼

Yes, you can archive multiple OpenSpec changes safely using a controlled, single-confirm workflow. This batch operation validates statuses, counts tasks, and moves completed changes to an auditable archive path while preserving specs for traceability.

Does OpenSpec bulk archiving preserve auditable traces and original specifications?▼

OpenSpec bulk archiving preserves auditable traces and original specifications by moving completed changes into date-stamped archive paths formatted as archive/YYYY-MM-DD-<name>. This ensures full traceability and historical reference for all batch-archived changes.

What is the best way to archive multiple completed OpenSpec changes without manual file operations?▼

The best way to archive multiple completed OpenSpec changes without manual file operations is using a bulk archive operation. It applies batch selection, validates completion status, and automatically generates date-stamped directories with preserved specs and audit records.