skills.rest
UnterrainerInformatik
UnterrainerInformatikOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion.

Updated Apr 20, 2020
Search Tags:#workflow#cli#archive#change management#spec-driven development#openspec#delta specs
One-click install
npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill openspec-archive-change-unterrainerinformatik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/UnterrainerInformatik/java-rdb-utils/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/UnterrainerInformatik/java-rdb-utils --skill openspec-archive-change-unterrainerinformatik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves checking artifact status, verifying task completion, syncing delta specs, and moving directories—steps that are easy to forget or perform inconsistently when done manually. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md before archiving, warning you about anything unfinished. - Delta Spec Sync Assessment: Compares delta specs against main specs and offers to sync changes before archiving. - Date-Stamped Archiving: Moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name> with collision detection. - Use Case: After finishing implementation of a feature change, invoke this Skill to confirm all artifacts and tasks are done, optionally sync specs, and archive the change with a clear summary. ## Quick Start Archive the completed change 'add-user-auth' after checking its artifact and task completion status.

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 change in OpenSpec?▼

Run the archive workflow with a change name, or let it prompt you to select from active changes listed by openspec list. It verifies completion, optionally syncs delta specs, then moves the change to openspec/changes/archive with a date prefix.

What happens if tasks are incomplete when archiving an OpenSpec change?▼

The workflow counts incomplete tasks marked with '- [ ]' in tasks.md and displays a warning with the count. You are asked to confirm before proceeding, so archiving is not blocked but you are informed.

Does archiving an OpenSpec change sync delta specs automatically?▼

No, it assesses delta specs against main specs and shows a summary of pending changes first. You can choose to sync now, archive without syncing, or cancel, and syncing is delegated to the openspec-sync-specs skill.

What if the archive target directory already exists?▼

The archive fails with an error if a directory named YYYY-MM-DD-<change-name> already exists in openspec/changes/archive. You are advised to rename the existing archive or use a different date.

What are the requirements for using the OpenSpec archive workflow?▼

You need the openspec CLI installed and a project structured with openspec/changes directories. The change should have artifacts trackable via openspec status and optionally a tasks.md file.

Related Skills

Explore More Software Engineering Skills→
zabinyzabiny
2

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta-spec status.

Official
Advanced
amauryconstantamauryconstant
6

osx-generate-changelog

Generate a CHANGELOG.md from archived OpenSpec changes using Keep a Changelog format.

Community
Intermediate
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