skills.rest
Yager-42
Yager-42COMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed changes after validating artifacts and tasks.

Updated Dec 26, 2025
Search Tags:#automation#workflow#archive#openspec#change-management#artifact-status#delta-specs
One-click install
npx skills add https://github.com/Yager-42/-- --skill openspec-archive-change-yager-42
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Yager-42/--/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/Yager-42/-- --skill openspec-archive-change-yager-42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in an experimental workflow, providing guardrails to verify artifacts, check tasks, and optionally synchronize delta specs before archiving.

Core Features & Use Cases

  • Prompts for a change name if not provided, and lists only active changes to archive.
  • Checks artifact completion via openspec status and warns about any incomplete artifacts.
  • Checks task completion in tasks.md and prompts before archiving if tasks are incomplete.
  • Analyzes delta specs against main specs and suggests syncing options, preserving safety.
  • Archives the change into openspec/changes/archive/YYYY-MM-DD-<name>, preserving .openspec.yaml and moving the directory atomically.
  • Provides a post-archive summary with location and status.

Quick Start

Provide the change name to begin the archive, or allow me to prompt you to choose from active changes.

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 changes in an openspec workflow?▼

To archive completed changes, the system validates artifact and task completion, optionally syncs delta specs, and moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name> while preserving configuration. You provide a change name or select from active ones to begin.

What happens if I try to archive a change with incomplete tasks or artifacts?▼

When archiving a change with incomplete artifacts or tasks, the system checks completion via openspec status and tasks.md, warning about incomplete artifacts and prompting for confirmation before proceeding with the archive.

Can I sync delta specs with main specs during the archiving process?▼

Yes, during archiving, the system analyzes delta specs against main specs and suggests syncing options to preserve safety, ensuring your main specs remain updated before the change directory is moved.

Does the archiving process preserve openspec configuration files?▼

Yes, the archiving process preserves the .openspec.yaml configuration file and moves the change directory atomically to ensure a safe, auditable archive without losing your original settings.

What is the best way to manage and audit archived experimental changes?▼

The best way to manage archived experimental changes is using an automated archive process that moves directories to openspec/changes/archive/YYYY-MM-DD-<name> and provides a post-archive summary with the exact location and sync status for auditability.

Related Skills

Explore More Software Engineering Skills→
arestivoarestivo

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes while resolving delta-spec conflicts.

Community
Advanced
jacobcyjacobcy
6

openspec-archive-change

Archive completed OpenSpec changes with artifact status checks and spec synchronization.

Community
Advanced
Pony-UnicornPony-Unicorn
7

openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

Community
Advanced
AkaraChenAkaraChen
25

openspec-bulk-archive-change

Batch-archive completed changes by validating active changes and resolving spec conflicts.

Community
Advanced