openspec-bulk-archive-change

Archives completed OpenSpec changes by validating artifacts and resolving conflicts via delta syncs.

18|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/igamenovoer/houmao --skill openspec-bulk-archive-change-igamenovoer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/igamenovoer/houmao/tree/main/tests/fixtures/plain-agent-def/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/igamenovoer/houmao --skill openspec-bulk-archive-change-igamenovoer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec.

What problem does it solve?

This Skill solves the problem of manually archiving many completed OpenSpec changes, especially when overlapping spec deltas can create conflicts or uncertainty about what should be synced and archived.

Core Features & Use Cases

  • Batch archiving for completed changes: Moves multiple selected changes into an archive directory in one operation.
  • Status-driven validation: Checks active changes, artifact completion, and whether tasks are complete before archiving.
  • Conflict detection and codebase-based resolution: Detects overlapping delta capabilities across selected changes and decides which spec sync to apply by verifying implementation evidence and applying chronological precedence when needed.
  • Clear operator confirmation and reporting: Presents a consolidated status table, prompts once for final confirmation, then outputs success/skip/failure results plus spec-sync summaries.

Quick Start

Use the skill to archive all selected completed OpenSpec changes in a single batch after reviewing the generated status and conflict-resolution plan.

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 archive multiple completed OpenSpec changes at once without causing spec delta conflicts?

Batch archiving OpenSpec changes requires validating artifact completion and detecting overlapping delta capabilities to ensure safe synchronization before moving files into a dated archive folder.

How does conflict resolution work when archiving parallel spec changes with overlapping capabilities?

Conflict resolution for overlapping spec deltas verifies implementation evidence in the codebase and applies chronological precedence to determine which spec sync to apply and in what order.

Do I need the openspec CLI to perform bulk change archiving and repository validation?

Yes, bulk archiving requires openspec CLI integration to validate active changes, check task completion, and execute interactive multi-select with explicit operator confirmation before moving changes.

What is the best way to manage spec sync when several parallel changes modify the same capability specs?

The best way to manage overlapping spec sync is by running codebase evidence checks to determine which spec deltas to sync chronologically, preventing conflicts before archiving completed changes.

Why does OpenSpec skip certain changes during a bulk archive operation?

OpenSpec skips changes during bulk archiving when status-driven validation detects incomplete artifacts or unfinished tasks, ensuring only fully completed changes move into the archive directory.

Can I select which completed changes to archive instead of processing all active changes automatically?

Yes, you can use interactive multi-select to choose specific completed changes for batch archiving, followed by a single explicit confirmation prompt to execute the operation safely.