skills.rest
benjaminkitt
benjaminkittCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed changes with artifact validation and delta-spec synchronization.

Updated Apr 14, 2026
Search Tags:#workflow#archive#openspec#changes#artifact-status#delta-specs#spec-sync
One-click install
npx skills add https://github.com/benjaminkitt/mindful-engineer --skill openspec-archive-change-benjaminkitt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/benjaminkitt/mindful-engineer/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/benjaminkitt/mindful-engineer --skill openspec-archive-change-benjaminkitt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed experimental changes to keep the workspace clean and preserve historical context.

Core Features & Use Cases

  • Archive completed changes after implementation to preserve final state.
  • Validate artifact completion and task status before archiving.
  • Optional delta-spec synchronization to align with main specs.

Quick Start

Archive a completed change by optionally specifying a change name; if omitted, select an active, non-archived change and proceed through artifact checks, delta spec sync, and final archival.

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 changes in an OpenSpec workflow?▼

Archiving completed changes involves selecting a finished change, verifying artifact completion and task status, optionally analyzing delta-spec differences, and executing the archival step to generate a summarized report with guardrail warnings.

What are delta specs and when do I need to sync them before archiving?▼

Delta specs represent incremental specification differences generated during active changes. You optionally sync them before archiving to align experimental modifications with main specs, ensuring the archived final state preserves accurate consolidated specification history.

Can I archive a change without manually checking task status and artifacts?▼

No, the skill enforces guardrails by automatically validating artifact completion and task status before proceeding, ensuring only fully completed changes move into the organized archive for long-term historical storage.

What is the best way to preserve historical context for completed experimental changes?▼

Archiving completed experimental changes into an organized directory keeps the workspace clean while validating completion status and storing a summarized final state report, providing the best way to preserve long-term historical context.

Why does change archival fail with incomplete artifacts or active task warnings?▼

Archival fails or warns because the skill enforces guardrails validating artifact completion and task status, reporting warnings to prevent archiving incomplete work and ensuring the organized archive only contains fully finalized changes.

Related Skills

Explore More Software Engineering Skills→
sanfordzhangsanfordzhang
1

openspec-bulk-archive-change

Batch-archive completed openspec changes with conflict-aware delta-spec handling.

Community
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
accidental-hedge-fundaccidental-hedge-fund
3

openspec-archive-change

Archive completed openspec experimental changes to dated directories with validation.

Official
Intermediate