skills.rest
AdJIa
AdJIaCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed change directories into dated paths with validation.

Updated Jan 29, 2026
Search Tags:#workflow#validation#audit#archive#openspec#change#delta-specs
One-click install
npx skills add https://github.com/AdJIa/markdown-x --skill openspec-archive-change-adjia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/AdJIa/markdown-x/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/AdJIa/markdown-x --skill openspec-archive-change-adjia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives completed changes from the experimental workflow to maintain a clean, auditable history and prevent confusion over release states.

Core Features & Use Cases

  • End-to-end archiving: securely moves finished change directories into a dated archive, preserving metadata and configuration.
  • Validation and guardrails: checks artifact and task completion, prompts for confirmation, and optionally syncs delta specs before archiving.
  • Audit-friendly summaries: generates a concise report including change name, schema used, archive path, and sync status.
  • Use Case: a developer has completed a change and wants to archive it for release management while keeping artifacts intact and delta spec state traceable.

Quick Start

Archive the latest completed change named <change> to the archive directory with the current date and preserved metadata.

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 workflow changes while preserving metadata?▼

To archive completed workflow changes, you can automate the process by moving the change directory into a dated archive path. This preserves metadata and configuration while maintaining an auditable history of release states.

What validation is needed before archiving a change directory?▼

Validation before archiving checks artifact and task completion to ensure the change is truly finished. The workflow prompts for confirmation, validates status via openspec commands, and optionally synchronizes delta specs to preserve traceability.

When should I archive delta specs in my change workflow?▼

You should archive delta specs when developers have finalized changes, verified artifacts, and confirmed task completion. Archiving at this stage prevents confusion over release states and maintains a clean, auditable project history.

Can I sync delta specs before moving a change to the archive path?▼

Yes, you can optionally synchronize delta specs before archiving. The archival process implements guardrails that prompt for change selection, validate completion status, and sync delta specs before securely moving the directory into a dated archive.

Does the archival process generate an audit summary for release management?▼

Yes, the archival process generates an audit-friendly summary report. This concise report includes the change name, schema used, the dated archive path, and the sync status to ensure release management has full traceability.

Related Skills

Explore More Software Engineering Skills→
MaplumeXMaplumeX

openspec-archive-change

Archive completed openspec changes with validation and delta-spec synchronization checks.

Community
Advanced
esneiderbravoesneiderbravo
1

openspec-archive-change

Archive completed OpenSpec changes into a date-stamped directory with status checks.

Community
Advanced
danielsogldanielsogl
39

openspec-archive-change

Archive completed OpenSpec changes after validating delta-spec synchronization.

Community
Advanced
KisthannyKisthanny
1

openspec-archive-change

Archive completed OpenSpec change directories after validating readiness and preserving workflow context.

Community
Advanced