skills.rest
DarkHighness
DarkHighnessCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes with validated artifacts and date-stamped paths.

11|3|Updated Dec 20, 2025
Search Tags:#workflow#validation#archive#openspec#audit-trail#change#spec-sync
One-click install
npx skills add https://github.com/DarkHighness/coi-public --skill openspec-archive-change-darkhighness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/DarkHighness/coi-public/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/DarkHighness/coi-public --skill openspec-archive-change-darkhighness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes to close out implementations and preserve a traceable archive.

Core Features & Use Cases

  • Validates artifact and task completion before archiving.
  • Compares delta specs to main specs and optionally syncs before archiving.
  • Preserves history and guarantees traceability for audits.

Quick Start

Provide the change name when prompted and follow the guided prompts to verify artifacts, tasks, and delta specs before archiving.

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 preserve an audit trail?▼

Archiving OpenSpec changes requires validating artifact completion, checking for incomplete tasks, and assessing delta-spec synchronization before moving the change into a date-stamped archive path for traceable history.

What happens if I try to archive an OpenSpec change with incomplete tasks?▼

The archival workflow validates task completion before proceeding. If incomplete tasks are detected, the process prevents the change from being moved into the archive until all tasks are resolved.

Do I need the OpenSpec CLI to archive changes and sync delta specs?▼

Yes, the OpenSpec CLI is required to archive changes. The skill uses the CLI to validate artifacts, assess delta-spec synchronization against main specs, and move changes into the archive.

Can I synchronize delta specs with main specs before archiving an OpenSpec change?▼

Yes, the archival process compares delta specs to main specs and optionally syncs them before archiving. This ensures the archived change reflects the finalized implementation state accurately.

When should I archive an OpenSpec change during the development workflow?▼

You should archive an OpenSpec change during change handoffs, post-implementation reviews, and archival workflows after an implementation is finalized and all artifacts are validated.

Related Skills

Explore More Software Engineering Skills→
epamepam
503

openspec-archive-change

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

Official
Advanced
Alan-TheGentlemanAlan-TheGentleman
10

sdd-archive

Merge delta specs into main specs and archive completed changes.

Community
Advanced
alexei-lexxalexei-lexx

openspec-verify-change

Validate alignment between openspec change artifacts and implemented code.

Community
Advanced
yandiaanyandiaan
2

openspec-archive-change

Archive completed OpenSpec changes with date-prefixed directories.

Community
Advanced