skills.rest
lbrlabs
lbrlabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with metadata preservation.

9|4|Updated Jun 13, 2023
Search Tags:#workflow#cli#archive#openspec#change-management#delta-spec#artifact-status
One-click install
npx skills add https://github.com/lbrlabs/pulumi-lbrlabs-eks --skill openspec-archive-change-lbrlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/lbrlabs/pulumi-lbrlabs-eks/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/lbrlabs/pulumi-lbrlabs-eks --skill openspec-archive-change-lbrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental OpenSpec workflow to finalize and preserve artifacts.

Core Features & Use Cases

  • Checks artifact completion, delta spec sync status, and archive path
  • Preserves metadata and .openspec.yaml during archiving
  • Relocates the change to openspec/changes/archive/YYYY-MM-DD-<name> after confirmation

Quick Start

Provide the change name to archive, then follow the prompts to complete the archival process.

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 after implementation?▼

OpenSpec change archival checks artifact completion, delta spec synchronization, and archive path validity before relocating the change directory to openspec/changes/archive/YYYY-MM-DD-<name> after confirmation.

What does OpenSpec artifact completion checking evaluate before archiving a change?▼

Artifact completion checking evaluates the status of workflow artifacts and delta spec synchronization to ensure all implementation deliverables are finalized before the change is safely relocated to the archive directory.

Do I need the openspec CLI to finalize and archive delta specs?▼

Yes, the openspec CLI is required to inspect artifact status, assess delta spec synchronization, preserve filesystem metadata, and relocate changes to openspec/changes/archive/YYYY-MM-DD-<name>.

How does OpenSpec preserve filesystem metadata when archiving completed changes?▼

OpenSpec preserves filesystem metadata and .openspec.yaml during archival relocation, ensuring the archived change retains its original artifact structure and delta spec integrity under openspec/changes/archive.

When should I archive an OpenSpec change instead of keeping it active?▼

Archive an OpenSpec change after implementation is finalized, artifact completion checks pass, and delta spec synchronization is assessed. This preserves the completed workflow artifacts safely in the archive directory.

Can I use OpenSpec change archival for incomplete workflow artifacts?▼

No, archival applies when finalizing a change after implementation. The process requires artifact completion checks to pass and delta spec synchronization to be assessed before relocating to the archive directory.

Related Skills

Explore More Software Engineering Skills→
sanfordzhangsanfordzhang
1

openspec-archive-change

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

Community
Advanced
mufengbufengmufengbufeng
1

openspec-archive-change

Archive completed changes to date-prefixed paths with openspec CLI.

Community
Advanced
epamepam
503

openspec-archive-change

Validate and archive completed Openspec workflow changes while preserving configuration files.

Official
Advanced
CatsofsufferingCatsofsuffering
5

openspec-archive-change

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

Community
Advanced