openspec-bulk-archive-change

Archive multiple completed openspec changes and resolve spec conflicts.

3|Updated Jan 27, 2026

Search Tags:#archive #conflict resolution #openspec #spec management #codebase validation #batch process

Ready to run

npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill openspec-bulk-archive-change-agentic-engineering-agency

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/Agentic-Engineering-Agency/specsafe/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill openspec-bulk-archive-change-agentic-engineering-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes by intelligently handling spec conflicts and validating implementation status, preventing manual errors and saving significant time.

Core Features & Use Cases

Batch Archiving: Archive several changes in a single operation.
Conflict Resolution: Automatically detects and resolves conflicts when multiple changes affect the same capability by checking the codebase.
Status Validation: Verifies artifact status, task completion, and delta specs before archiving.
Use Case: When you have finished developing several related features (e.g., authentication, user profiles, and permissions), you can use this skill to archive them all at once, ensuring that their specifications are correctly merged or prioritized based on actual implementation.

Quick Start

Use the openspec-bulk-archive-change skill to archive all completed changes.

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 multiple completed openspec changes at once?▼

To batch archive completed openspec changes, you can automate the process to move multiple specifications to an archive directory in a single operation. The system intelligently resolves spec conflicts and validates implementation status before archiving.

What is the best way to resolve spec conflicts when archiving codebase changes?▼

Resolving spec conflicts during archiving is handled automatically by inspecting the codebase for implementation evidence. The system synchronizes conflicting specifications by prioritizing them based on actual implementation in the codebase.

How does spec management validate implementation status before archiving?▼

Spec management validates implementation status by verifying artifact status, task completion, and delta specs before archiving. This ensures only fully completed changes are moved to the archive directory.

Can I select specific completed changes to archive in a batch process?▼

Yes, the batch process includes user prompts for selection and confirmation steps. You can select specific completed changes to archive, ensuring safe and efficient batch operations tailored to your needs.

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

Bulk archiving is ideal when you have finished developing several related features, such as authentication and user profiles. It prevents manual errors and saves significant time by merging specifications correctly in one operation.