skills.rest
Lerr1uqs
Lerr1uqsCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes with validation and date-prefixed directory moves.

Updated Mar 21, 2026
Search Tags:#workflow#validation#archive#openspec#audit-trail#change-management
One-click install
npx skills add https://github.com/Lerr1uqs/openjarvis --skill openspec-archive-change-lerr1uqs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Lerr1uqs/openjarvis/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/Lerr1uqs/openjarvis --skill openspec-archive-change-lerr1uqs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes to preserve history, ensure proper archiving workflows, and prevent rework on finalized artifacts.

Core Features & Use Cases

  • Safe archiving: moves a finished change into openspec/changes/archive with a date-prefixed folder name.
  • Validation and prompts: checks artifacts and tasks, prompts for user confirmation when incomplete or ambiguous.
  • Delta spec synchronization: assesses delta specs against main specs and optionally syncs before archiving.
  • Audit trail: preserves .openspec.yaml and maintain traceability for future reference.

Quick Start

Archive a completed change by selecting the target change, validating artifacts, and moving the change to the archive directory with a date-prefixed 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 safely?▼

Archiving completed changes requires moving the finished change directory into openspec/changes/archive with a date-prefixed folder name, validating artifacts and tasks first, and preserving the .openspec.yaml file to maintain a full audit trail.

What happens to delta specs when archiving an openspec change?▼

Before archiving an openspec change, the skill assesses delta specs against main specs and optionally syncs them, ensuring the archived artifacts reflect the finalized project state accurately.

Can I archive a change if tasks or artifacts are incomplete?▼

If tasks or artifacts are incomplete or ambiguous, the validation step detects this and prompts the user for confirmation before proceeding to move the change directory into the archive.

Do I need to manually specify which change to archive in openspec?▼

You do not need to manually specify a change; if none is provided, the skill prompts you to select from active changes and displays available schemas to proceed with the archiving workflow.

Why does openspec use a date-prefixed folder name for archived changes?▼

Using a date-prefixed folder name like YYYY-MM-DD-<name> preserves chronological history and maintains traceability, ensuring finalized artifacts are kept in a structured, auditable archive directory.

Related Skills

Explore More Software Engineering Skills→
QuafadasQuafadas
13

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta specs.

Community
Advanced
studyzystudyzy
10.2k

openspec-archive-change

Archive completed OpenSpec experimental changes into date-prefixed directories.

Community
Advanced
lz-freedomlz-freedom

openspec-archive-change

Archive validated openspec changes into dated archive folders with metadata.

Community
Advanced
rick2047rick2047

openspec-archive-change

Archive completed OpenSpec changes with finalized delta specs and artifacts.

Community
Advanced