skills.rest
bill80362
bill80362COMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion.

Updated Aug 14, 2026
Search Tags:#cli#archive#change management#openspec#task verification#spec workflow
One-click install
npx skills add https://github.com/bill80362/laravel-thread-admin --skill openspec-archive-change-bill80362
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/bill80362/laravel-thread-admin/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/bill80362/laravel-thread-admin --skill openspec-archive-change-bill80362

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in the OpenSpec experimental workflow requires checking artifact status, task completion, and delta spec sync state before moving files into an archive directory. Doing this manually is error-prone and can leave specs out of sync. ## Core Features & Use Cases - Completion Verification: Runs openspec status --json to check artifact completion and scans tasks.md for incomplete checklist items before archiving. - Delta Spec Sync Assessment: Compares delta specs against main specs and optionally triggers the openspec-sync-specs workflow before archiving. - Safe Archiving: Moves the change directory into a date-prefixed archive folder (YYYY-MM-DD-name) with collision detection and user confirmation prompts. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the skill verifies all artifacts and tasks are done, offers to sync specs, then moves the change into the archive with a summary report. ## Quick Start Archive the completed change named add-user-auth and confirm any warnings about incomplete artifacts or tasks.

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 skill list active changes via openspec list --json so you can select one. It verifies artifact and task completion, then moves the change directory into an archive folder named with the current date.

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

The skill 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 but you stay informed.

Does archiving sync delta specs to the main specs?▼

Before archiving, the skill compares delta specs against main specs at openspec/specs/<capability>/spec.md and shows a summary. You can choose to sync via the openspec-sync-specs workflow or archive without syncing.

Can I archive workspace-planning changes with openspec?▼

No. If 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.

What happens if an archive with the same date and name already exists?▼

The archive fails with an error suggesting you rename the existing archive or use a different date. The skill checks for target collisions before moving the change directory.

Related Skills

Explore More Software Engineering Skills→
carlosapgomescarlosapgomes

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
psaccpsacc

openspec-onboard

Guide users through the complete OpenSpec workflow from idea to implementation.

Community
Advanced
cynkracynkra
1

openspec-sync-specs

Merge delta OpenSpec requirement blocks into main spec files per capability.

Official
Intermediate
MiDouTechMiDouTech

openspec-archive-change

Archive completed openspec changes into date-prefixed directories after verification.

Official
Advanced