opsx-archive

Archive completed OpenSpec changes with spec sync, changelog updates, and issue closure.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Finalizing a completed change in an OpenSpec-driven workflow involves many manual steps: verifying artifacts and tasks, syncing delta specs, moving directories, updating changelogs and feature docs, and closing GitHub issues. This Skill orchestrates that entire archival process with validation gates so nothing is archived prematurely or left inconsistent. ## Core Features & Use Cases - Completion validation: Checks artifact status via openspec status --json, reconciles tasks.md against GitHub tracking issues, and blocks archiving when required work is incomplete unless the user explicitly overrides. - Spec and documentation sync: Compares delta specs against main specs, converts test-plan cases into reusable TS-NNN test scenario files, updates feature docs, and appends a Keep a Changelog entry. - Use Case: After finishing the register-export change, run the archive command to move it into openspec/changes/archive/YYYY-MM-DD-register-export/, sync its delta specs, update CHANGELOG.md, and close the linked GitHub issue in one guided flow. ## Quick Start Ask the assistant to archive the completed change named register-export using the opsx-archive workflow.

Frequently Asked Questions about opsx-archive

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

FAQPage Schema
How do I archive a completed OpenSpec change?

Run the archive command with the change name, for example /opsx-archive register-export. The skill verifies artifact and task completion, syncs delta specs, moves the directory to openspec/changes/archive/YYYY-MM-DD-<name>/, and updates the changelog.

What happens if I archive a change with incomplete tasks?

The archive is blocked and the incomplete tasks are listed by name. You can either go back and finish the work or explicitly choose the override option to archive anyway, which adds a warning note to the archive summary.

Does archiving sync delta specs to the main specs?

Yes. If delta specs exist under the change's specs directory, the skill compares them with the main specs, shows a combined summary of additions, modifications, and removals, and prompts you to sync before archiving.

Can the archive skill close the GitHub tracking issue automatically?

It reads plan.json for the tracking_issue number and asks for confirmation. If approved, it closes the issue via GitHub MCP update_issue or the gh issue close CLI fallback with an archive comment.

Why does archiving fail with a target already exists error?

The archive target uses the current date, so archiving the same change twice on one day collides. Rename or remove the existing dated archive directory, or wait until a different date to retry.