source-command-opsx-archive

Archive completed openspec experimental workflow changes with validation checks.

9|1|Updated May 13, 2026

Search Tags:#archive #openspec #task-tracking #change-management #artifact-validation #spec-sync #experimental-workflow

Ready to run

npx skills add https://github.com/susomejias/rembric --skill source-command-opsx-archive

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-command-opsx-archive
Source: https://github.com/susomejias/rembric/tree/main/.agents/skills/source-command-opsx-archive
Command: npx skills add https://github.com/susomejias/rembric --skill source-command-opsx-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually archiving completed changes in experimental openspec workflows risks missing validation checks, skipping spec syncs, or overwriting existing archives, leading to lost work and inconsistent documentation.

Core Features & Use Cases

Pre-archive Validation: Automatically checks artifact completion status and incomplete tasks to warn users before archiving unfinished work.
Delta Spec Sync Assessment: Evaluates unmerged delta specs and prompts users to sync changes to main specs before archiving to avoid spec drift.
Use Case: Development teams using the openspec experimental workflow can use this skill to safely archive completed feature changes, ensuring all work is properly validated and specs are up to date before moving work to the archive.

Quick Start

Use the source-command-opsx-archive skill to archive the completed experimental change named add-auth after confirming all artifacts and tasks are finished.

Frequently Asked Questions about source-command-opsx-archive

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

FAQPage Schema

How do I safely archive completed openspec experimental workflow changes?▼

Archiving completed openspec experimental workflow changes safely requires automating artifact completion checks, verifying task statuses, and assessing delta spec syncs to prevent manual validation errors and missed documentation updates.

What happens if I try to archive incomplete tasks in an experimental workflow?▼

Pre-archive validation automatically checks artifact completion status and incomplete tasks, warning users before archiving unfinished work to ensure no experimental changes are lost or improperly documented.

How do I prevent spec drift when archiving openspec experimental features?▼

Preventing spec drift during archiving involves assessing unmerged delta specs and prompting users to sync changes to main specs before moving the completed experimental feature changes to the archive.

Can I avoid overwriting existing archives when managing openspec changes?▼

Avoiding overwrites in openspec change management is handled by creating dated archive directories, ensuring previously archived experimental workflow changes remain intact and preventing the loss of historical work.

Do I need to sync delta specs to main specs before archiving openspec work?▼

Syncing delta specs to main specs before archiving is optional but recommended, as the archival process assesses unmerged deltas and prompts users to sync changes to avoid documentation drift.

What is the best way to automate change management validation for openspec workflows?▼

Automating change management validation for openspec workflows is best handled by a tool that checks artifact completion, verifies task status, and evaluates delta spec syncs to eliminate manual oversight.