opsx-archive

Archives completed OpenSpec changes via the /opsx:archive slash command.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill opsx-archive-te-quanbzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsx-archive
Source: https://github.com/TE-QuanBZhang/skills-pool/tree/main/ai-coding/skills/opsx-archive
Command: npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill opsx-archive-te-quanbzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks—verifying task completion, syncing delta specs, and moving the change directory into a dated archive folder. This Skill automates that finalization process through a single slash command. ## Core Features & Use Cases - Completion Verification: Checks change status via openspec status --change and reads tasks.md for incomplete items before archiving. - Delta Spec Sync: Offers to synchronize delta specifications before archiving when they exist. - Dated Archiving: Moves the change directory into archive/YYYY-MM-DD-<name> and displays a summary. - Use Case: After finishing implementation of an add-auth change, invoke /opsx:archive add-auth to verify all tasks are done, sync specs, snapshot context with CodeGraph, and archive the change folder. ## Quick Start Ask the AI to run /opsx:archive with your change name to verify completion and archive the finished OpenSpec change.

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?

Invoke /opsx:archive optionally followed by the change name, such as /opsx:archive add-auth. The skill checks completion status, syncs delta specs if present, and moves the change directory into a dated archive folder.

What happens if tasks are incomplete when archiving a change?

The skill reads tasks.md and checks for incomplete items before archiving. It also runs openspec status --change with JSON output to verify the change state, so unfinished work is surfaced before finalization.

Does opsx-archive require the openspec CLI?

Yes, the skill requires the openspec CLI to run status checks on changes. It also works alongside the other OpenSpec workflow skills and optionally uses CodeGraph for context snapshots.

Where are archived OpenSpec changes stored?

Archived changes are moved into the changes directory under archive/ with a date-prefixed folder name in the format YYYY-MM-DD-<name>. A summary is shown after the move completes.

Can I archive a change without specifying its name?

Yes, the change name is optional. If omitted or ambiguous, the skill prompts you to select the correct change before proceeding with the archive workflow.