skills.rest
fjpulidop
fjpulidopCOMMUNITY
Explore all skills by this author →
GitHub

opsx-archive

Archive completed openspec workflow changes with date-based names and summaries.

9|2|Updated Mar 12, 2026
Search Tags:#workflow#audit#archive#openspec#delta-spec#artifact-status
One-click install
npx skills add https://github.com/fjpulidop/specrails-core --skill opsx-archive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opsx-archive
Source: https://github.com/fjpulidop/specrails-core/tree/main/specrails-plugin/skills/opsx-archive
Command: npx skills add https://github.com/fjpulidop/specrails-core --skill opsx-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow to ensure proper archival and reference.

Core Features & Use Cases

  • Checkpoints ensure artifact completion status via openspec status, delta spec sync assessment, and archiving.
  • Guardrails prompt for change selection when not provided and preserve configuration files like .openspec.yaml.
  • Auditability maintains an organized archive with date-based naming and a summary.

Quick Start

Archive a completed change by choosing a change and following the prompts to archive.

Frequently Asked Questions about opsx-archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive completed changes in the openspec workflow?▼

To archive openspec changes, validate artifact completion and delta spec sync status, then move the change to openspec/changes/archive using a date-based name. The process preserves configuration files like .openspec.yaml and provides a summary of archived items.

What happens if I try to archive an incomplete openspec change?▼

Archiving an incomplete openspec change triggers a warning. The workflow checks artifact completion status and delta spec sync assessment before archiving, ensuring only properly finished changes are moved to the archive directory.

How does delta spec sync status affect archiving experimental workflow changes?▼

Delta spec sync status is assessed before archiving openspec changes. You can optionally sync specs before archiving to ensure the archive reflects the latest state, preventing outdated artifacts from being stored.

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

No, you do not need to manually specify. Guardrails prompt for change selection when it is not provided, ensuring you select the correct openspec change before the archiving process proceeds.

Are configuration files preserved when archiving openspec changes?▼

Yes, configuration files like .openspec.yaml are preserved during archiving. The process securely archives the completed openspec change while maintaining necessary configuration files intact for auditability.

When should I use date-based naming for archived workflow artifacts?▼

Date-based naming should be used when archiving completed openspec changes to maintain an organized archive. This auditability feature ensures clear chronological reference and tracking for archived experimental workflow artifacts.

Related Skills

Explore More Software Engineering Skills→
esneiderbravoesneiderbravo
1

openspec-archive-change

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

Community
Advanced
dorriodorrio

openspec-archive-change

Archive completed changes with verified artifacts and optional delta spec syncing.

Community
Advanced
garethbaumgartgarethbaumgart
1

openspec-archive-change

Validate artifacts and tasks, then archive completed changes to a dated folder.

Community
Advanced
crozzbitecrozzbite

openspec-new-change

Scaffold a new OpenSpec change with a default artifact workflow.

Community
Intermediate