openspec-bulk-archive-change

Archive multiple completed OpenSpec changes while detecting spec conflicts.

4|1|Updated Jan 16, 2026

Search Tags:#automation #cli #openspec #change-management #bulk-archive #spec-conflict

Ready to run

npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-bulk-archive-change-jankneumann

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-bulk-archive-change-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines the process of archiving several completed OpenSpec changes at once, eliminating the need to handle each change manually and ensuring spec conflicts are resolved safely.

Core Features & Use Cases

Batch Archiving: Moves multiple active changes to an archive folder in a single operation.
Conflict Detection: Identifies and resolves spec conflicts across selected changes before archiving.
Status Validation: Checks artifact completion, task lists, and delta specs to ensure readiness.
User Confirmation: Prompts the user to confirm selections and final actions, providing transparent summaries.
Use Case: When a development team has finished several feature changes and wants to clean up the repository while preserving spec integrity.

Quick Start

Invoke the openspec bulk archive change skill, follow the prompts to select the changes, and confirm the archive operation.

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

The bulk archive operation detects and resolves spec conflicts across selected changes before moving them, ensuring artifact completion, task lists, and delta specs are validated to preserve spec integrity.

Can I batch move active changes to an archive folder without spec conflicts?▼

Yes, the bulk archive operation detects and resolves spec conflicts across selected changes before moving them, ensuring artifact completion, task lists, and delta specs are validated to preserve spec integrity.

What do I need to run bulk archive operations for OpenSpec changes?▼

No, the bulk archive process prompts you to confirm your selected changes and final actions, providing transparent summaries so you can verify selections before any directories are moved.

Do I need shell command permissions to move OpenSpec change directories?▼

Yes, the bulk archive process prompts you to confirm your selected changes and final actions, providing transparent summaries so you can verify selections before any directories are moved.

How does status validation work when archiving OpenSpec changes?▼

No, the bulk archive process prompts you to confirm your selected changes and final actions, providing transparent summaries so you can verify selections before any directories are moved.

When should I use bulk archiving instead of archiving changes individually?▼

No, the bulk archive process prompts you to confirm your selected changes and final actions, providing transparent summaries so you can verify selections before any directories are moved.