skills.rest
seanmars
seanmarsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Updated Jan 18, 2026
Search Tags:#automation#versioning#archive#openspec#workflow-management#delta-specs#artifact-check
One-click install
npx skills add https://github.com/seanmars/ai-coding-setup --skill openspec-archive-change-seanmars
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/seanmars/ai-coding-setup/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/seanmars/ai-coding-setup --skill openspec-archive-change-seanmars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed OpenSpec change and preserve a verifiable record of its state.

Core Features & Use Cases

  • Prompt for a change if not provided
  • Verify artifact status via openspec status --json
  • Confirm task completion via tasks.md
  • Assess delta specs and sync state against main specs
  • Archive to openspec/changes/archive/YYYY-MM-DD-<name> while preserving .openspec.yaml
  • Provide a clear summary of actions and any warnings

Quick Start

Archive a completed OpenSpec change by selecting it, validating artifacts and tasks, optionally syncing delta specs, and moving it to openspec/changes/archive/YYYY-MM-DD-<name>.

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 completed OpenSpec changes while preserving the configuration file?▼

To archive OpenSpec changes, the workflow moves completed changes into openspec/changes/archive/YYYY-MM-DD-<name> while preserving the .openspec.yaml file, ensuring a verifiable record of the state is safely maintained.

What is the best way to verify task completion before archiving an OpenSpec change?▼

Verifying task completion before archiving an OpenSpec change involves checking the tasks.md file to confirm all required tasks are finished before the change is moved to the archive directory.

How does delta spec synchronization work when finalizing an OpenSpec workflow?▼

Delta spec synchronization during OpenSpec archival assesses delta specs and syncs their state against main specs, ensuring experimental modifications are properly reconciled before the change is archived.

Can I validate artifact status automatically before moving changes to the archive?▼

You can validate artifact status automatically by running openspec status --json, which checks artifacts and provides a clear summary of actions and warnings before the change is archived.

What happens to the .openspec.yaml file when an OpenSpec change is archived?▼

When an OpenSpec change is archived, the .openspec.yaml file is preserved within the archive directory structure at openspec/changes/archive/YYYY-MM-DD-<name>, keeping the configuration intact.

Why does my OpenSpec archival process generate warnings about delta specs?▼

OpenSpec archival generates warnings about delta specs when they are compared against main specs and discrepancies are found. The workflow assesses delta specs, syncs state, and reports unresolved issues in the summary.

Related Skills

Explore More Software Engineering Skills→
goerngoern
113

openspec-archive-change

Archive completed OpenSpec changes into dated directories with validation.

Community
Advanced
aditriokaaditrioka

openspec-archive-change

Archive completed OpenSpec changes with artifact and task completion checks.

Community
Advanced
ilazinessilaziness
6

openspec-archive-change

Archive completed OpenSpec changes after validating tasks and syncing delta specs.

Community
Advanced
belingudbelingud
30

openspec-archive-change

Archive completed OpenSpec changes with verified artifacts and delta specs.

Community
Advanced