source-command-opsx-archive

Archives completed OpenSpec changes with artifact, task, and delta spec sync checks.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill source-command-opsx-archive-jonathanlin768
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-opsx-archive
Source: https://github.com/jonathanlin768/CS2Match-Nakama/tree/main/.agents/skills/source-command-opsx-archive
Command: npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill source-command-opsx-archive-jonathanlin768

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a change in an OpenSpec-driven workflow is finished, it must be moved out of the active changes directory without losing spec updates or hiding incomplete work. This Skill automates that archival process while verifying completion status first. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md before archiving, warning the user about anything unfinished. - Delta Spec Sync Assessment: Compares delta specs against main specs and offers to sync them via the openspec-sync-specs skill before archiving. - Safe Archive Operation: Moves the change directory into a dated archive folder (YYYY-MM-DD-<name>) and fails safely if the target already exists. - Use Case: After finishing the add-auth change, run the archive command to confirm all artifacts and tasks are done, sync spec deltas, and move the change into the archive with a clear summary. ## Quick Start Ask the assistant to archive the completed change named add-auth using the opsx archive command.

Frequently Asked Questions about source-command-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, such as /opsx:archive add-auth. The skill checks artifact and task completion, assesses delta spec sync state, then moves the change directory into an archive folder named with the current date.

What happens if I archive a change with incomplete tasks?

The skill counts incomplete tasks marked with unchecked boxes in tasks.md and displays a warning with the count. It prompts for confirmation and proceeds with the archive only if you approve.

Does the archive command sync delta specs to main specs?

Yes, when delta specs exist it compares them against the main specs and shows a summary of additions, modifications, and removals. You can choose to sync via the openspec-sync-specs skill or archive without syncing.

Why does archiving fail with a target already exists error?

The archive target uses the format YYYY-MM-DD-change-name, so archiving the same change twice on one day collides. Rename or delete the existing archive, or wait until a different date.

Can I archive a change in workspace-planning mode?

No. When the status JSON reports actionContext.mode as workspace-planning, the skill stops and explains that workspace archive is not supported. It does not move workspace changes into repo-local archives.