openspec-archive-change

Archives completed OpenSpec changes after verifying artifacts, tasks, and spec synchronization.

7|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/Printaga/PiLot --skill openspec-archive-change-printaga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Printaga/PiLot/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/Printaga/PiLot --skill openspec-archive-change-printaga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow requires checking artifact completion, task status, and delta spec synchronization before moving the change into an archive directory, which is error-prone when done manually. ## Core Features & Use Cases - Guided change selection: Resolves the target change from user input, conversation context, or an interactive prompt listing active changes. - Completion verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning before proceeding. - Delta spec sync assessment: Compares delta specs against main specs, optionally runs an inline sync workflow, and verifies the result before archiving. - Use Case: After finishing implementation of a change like add-user-auth, run the archive workflow to confirm all artifacts and tasks are done, sync spec deltas into the main specs, and move the change into the dated archive folder. ## Quick Start Ask the assistant to archive the completed OpenSpec change by name, for example by saying to archive the change 'add-user-auth' now that implementation is finished.

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?▼

Provide the change name or let the workflow infer it from context. It checks artifact and task completion, assesses delta spec sync state, then moves the change directory into an archive folder prefixed with the current date.

What happens if tasks are incomplete when archiving a change?▼

The workflow counts incomplete tasks marked with '- [ ]' in tasks.md and displays a warning with the count. It asks for confirmation before proceeding, so archiving is never blocked by warnings alone.

Does the archive workflow sync delta specs to main specs?▼

Yes, when delta specs exist it compares them against main specs and offers to sync. The sync runs inline and is verified before the change is moved; if verification fails, archiving stops.

Can I archive a change in a registered OpenSpec store?▼

Yes, run openspec store list --json to discover store ids, then pass --store <id> on commands that read or write specs and changes. The flag stays sticky for the rest of the workflow.

What happens if the archive target directory already exists?▼

The archive fails with an error suggesting you rename the existing archive or use a different date. The change directory is not moved, so nothing is lost.