skills.rest
patorn
patornCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes with date-stamped folders and status checks.

Updated May 29, 2026
Search Tags:#workflow#auditing#archive#openspec#change-management#delta-spec#artifact-status
One-click install
npx skills add https://github.com/patorn/langgraph-template --skill openspec-archive-change-patorn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/patorn/langgraph-template/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/patorn/langgraph-template --skill openspec-archive-change-patorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow to keep records clean and traceable.

Core Features & Use Cases

  • Automates archival of OpenSpec changes after implementation, including artifact and task status checks.
  • Supports optional delta-spec synchronization and clear post-archive summaries.
  • Use Case: When a change is validated and ready, run this Skill to archive it to openspec/changes/archive with a date-stamped folder.

Quick Start

Archive a completed change by moving the OpenSpec change directory to the archive folder.

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 to keep project records clean?▼

To archive completed OpenSpec changes, you move the change directory to the openspec/changes/archive folder with a date-stamped structure, preserving traceability and ensuring auditable records.

What does the OpenSpec change archival workflow check before moving artifacts?▼

The OpenSpec change archival workflow performs artifact and task status checks via the openspec CLI to verify that a change is validated and ready before executing safe move operations.

When should I archive a delta-spec in OpenSpec change management?▼

You should archive a delta-spec in OpenSpec change management when a change is fully validated and ready, utilizing the optional delta-spec synchronization to preserve metadata during the archival process.

Does OpenSpec archiving preserve metadata when moving completed changes?▼

Yes, OpenSpec archiving preserves metadata by using safe move operations that transfer the validated change directory to a date-stamped archive folder without losing traceability or auditable records.

What is the best way to automate OpenSpec change archiving after implementation?▼

The best way to automate OpenSpec change archiving is to use a multi-step workflow that validates artifact and task statuses via the openspec CLI, then performs date-based archiving with optional delta-spec synchronization.

Can I archive an OpenSpec change if artifact or task status checks fail?▼

Archiving an OpenSpec change requires artifact and task status checks to pass via the openspec CLI first; if these validation checks fail, the change is not ready and the safe move operation will not proceed.

Related Skills

Explore More Software Engineering Skills→
DataCoveyDataCovey
27

openspec-archive-change

Archive a completed OpenSpec change to preserve artifacts and align with the experimental workflow.

Official
Advanced
RamonsDkaRamonsDka
1

sdd-archive

Merge delta specs into main specs and archive change folders.

Community
Advanced
sanfordzhangsanfordzhang
1

openspec-archive-change

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

Community
Advanced
jankneumannjankneumann
4

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes while detecting spec conflicts.

Community
Advanced