skills.rest
esneiderbravo
esneiderbravoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

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

1|Updated Apr 17, 2026
Search Tags:#automation#workflow#archive#openspec#change-management#artifact-status#delta-specs
One-click install
npx skills add https://github.com/esneiderbravo/hackaton --skill openspec-archive-change-esneiderbravo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/esneiderbravo/hackaton/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/esneiderbravo/hackaton --skill openspec-archive-change-esneiderbravo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes and ensure a reproducible audit trail by safely moving finalized change directories into an organized archive, while preserving key metadata and prompts for optional sync status.

Core Features & Use Cases

  • Artifact and task status checks to confirm completion before archiving.
  • Delta-spec synchronization assessment with an option to run a sync.
  • Creation of a date-stamped archive directory under openspec/changes/archive.
  • Comprehensive, human-readable summary of the archival outcome for auditing and traceability.

Quick Start

Run the archive operation for a completed change to move it into the archive and generate a final status summary.

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 for a reproducible audit trail?▼

Archiving completed OpenSpec changes involves moving finalized change directories into an organized, date-stamped archive folder, which preserves key metadata and generates a human-readable summary for traceability.

What does the OpenSpec change archival process check before moving files?▼

The OpenSpec change archival process checks artifact completion, task status, delta-spec synchronization, and user confirmation before safely moving the change directory into the archive.

How do I know if my delta-specs are synchronized before archiving an OpenSpec change?▼

Delta-spec synchronization is assessed during the archival workflow, providing an option to run a sync operation and reporting the sync status within the final concise summary output.

Can I archive an OpenSpec change directory if tasks are not fully completed?▼

No, artifact and task status checks are performed to confirm completion before archiving, preventing incomplete OpenSpec changes from being moved into the date-stamped archive folder.

Where are finalized OpenSpec change directories stored after archival?▼

Finalized OpenSpec change directories are stored under openspec/changes/archive, organized with a date-stamped name to maintain a clear and reproducible audit trail.

What information is included in the OpenSpec archival summary output?▼

The archival summary output includes the change name, schema, archive location, sync status, and any warnings, providing a comprehensive overview for auditing and traceability purposes.

Related Skills

Explore More Software Engineering Skills→
llama-farmllama-farm
2

openspec-archive-change

Archive completed OpenSpec changes with delta-spec comparison and metadata preservation.

Official
Advanced
LIDR-academyLIDR-academy
273

openspec-archive-change

Archive completed openspec changes into date-based folders with validation and syncing checks.

Official
Advanced
CatsofsufferingCatsofsuffering
5

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with status checks.

Community
Advanced
belingudbelingud
30

openspec-archive-change

Archive completed OpenSpec changes with verified artifacts and delta specs.

Community
Advanced