openspec-archive-change

Archives completed OpenSpec changes and syncs delta specs into main specifications.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill openspec-archive-change-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/openspec-archive-change
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill openspec-archive-change-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed change proposals in an OpenSpec workflow accumulate in the active changes directory, cluttering the workspace and leaving delta specs disconnected from the main specification set. This Skill finalizes a deployed change by moving it into a dated archive and folding its delta specs into the canonical specs. ## Core Features & Use Cases - Guided change selection: Lists active changes via openspec list --json and prompts the user to pick one, never guessing or auto-selecting. - Completion and sync checks: Verifies artifact status with openspec status --json, counts incomplete tasks in tasks.md, and compares delta specs against main specs before archiving. - Safe dated archiving: Moves the change to openspec/changes/archive/YYYY-MM-DD-<name>/, failing safely if the target already exists. - Use Case: After deploying a feature tracked as an OpenSpec change, run the archive flow to confirm all artifacts and tasks are done, sync the delta specs into the main specification set, and store the change under a dated archive folder. ## Quick Start Ask the assistant to archive the deployed OpenSpec change named add-user-auth and sync its delta specs into the main specifications.

Frequently Asked Questions about openspec-archive-change

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 flow with a change name, or let it list active changes via openspec list --json so you can pick one. It checks artifact and task completion, offers to sync delta specs, then moves the change to openspec/changes/archive/YYYY-MM-DD-<name>/.

What happens to delta specs when archiving an OpenSpec change?▼

Before archiving, the Skill compares each delta spec under openspec/changes/<name>/specs/ with the corresponding main spec and shows a combined summary. You can choose to sync the deltas into the main specs via the openspec-sync-specs approach or archive without syncing.

Can I archive an OpenSpec change with incomplete tasks?▼

Yes, archiving is not blocked by incomplete tasks or artifacts. The Skill displays a warning listing incomplete artifacts or the count of unchecked tasks and asks you to confirm before proceeding.

Why does archiving fail with a target already exists error?▼

The archive target is named YYYY-MM-DD-<change-name>, so archiving the same change twice on one day collides. Rename the existing archived directory or archive on a different date to resolve the conflict.

Does archiving an OpenSpec change require the openspec CLI?▼

Yes, the openspec CLI is required. The Skill runs openspec list --json to enumerate active changes and openspec status --change <name> --json to check artifact completion before performing the archive.