opsx-bulk-archive

Archive multiple completed OpenSpec changes in one batch operation.

1|Updated Jul 16, 2026
One-click install
npx skills add https://github.com/ConductionNL/buildiq --skill opsx-bulk-archive-conductionnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opsx-bulk-archive
Source: https://github.com/ConductionNL/buildiq/tree/main/.claude/skills/opsx-bulk-archive
Command: npx skills add https://github.com/ConductionNL/buildiq --skill opsx-bulk-archive-conductionnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving completed OpenSpec changes one at a time is repetitive and error-prone, especially when multiple changes touch the same capability specs. This Skill batch-archives changes while detecting and resolving spec conflicts by inspecting the actual codebase. ## Core Features & Use Cases - Batch archiving: Select and archive multiple completed changes in a single operation, moving each to openspec/changes/archive/YYYY-MM-DD-<name>. - Conflict detection and resolution: Detects when 2+ changes touch the same capability spec, then checks the codebase to determine which changes are actually implemented and applies specs in chronological order. - Status validation: Verifies artifact completion, task checkboxes in tasks.md, and GitHub tracking issues before archiving, blocking incomplete changes unless explicitly overridden. - Housekeeping automation: Syncs delta specs to main specs, updates feature docs, merges entries into CHANGELOG.md using Keep a Changelog categories, and optionally closes GitHub tracking issues. - Use Case: After finishing a sprint with three completed changes (webhooks, pagination fix, CSV export), archive all three at once with spec sync and changelog updates handled automatically. ## Quick Start Ask the assistant to archive all completed OpenSpec changes in bulk and confirm the selection when prompted.

Frequently Asked Questions about opsx-bulk-archive

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

FAQPage Schema
How do I archive multiple OpenSpec changes at once?▼

Run the bulk archive skill, which lists all active changes via `openspec list --json` and prompts you to multi-select which ones to archive. It validates tasks and artifacts, syncs delta specs, then moves each change to `openspec/changes/archive/YYYY-MM-DD-<name>`.

What happens when two changes modify the same capability spec?▼

The skill detects the conflict and inspects the codebase for implementation evidence. If only one change is implemented, only its specs sync; if both are implemented, they apply in chronological order with the newer change taking precedence.

Can I archive a change with incomplete tasks?▼

By default no. Changes with unchecked tasks or incomplete artifacts are flagged and skipped. You can explicitly override to archive them, but the recommended option always archives only the ready changes.

Does bulk archive update the changelog automatically?▼

Yes. It reads the version from openspec/app-config.json or appinfo/info.xml, categorizes completed tasks using Keep a Changelog categories, and merges entries into CHANGELOG.md, creating the file if it does not exist.

Does it close GitHub issues after archiving?▼

If an archived change's plan.json contains a tracking_issue, the skill asks whether to close it. Closing uses the GitHub MCP update_issue and add_issue_comment tools, with `gh issue close` as a CLI fallback.