sdd-archive

Merges delta specs into main specs and archives completed SDD changes.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Balthael/ciberbal-ai --skill sdd-archive-balthael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/Balthael/ciberbal-ai/tree/main/internal/assets/skills/sdd-archive
Command: npx skills add https://github.com/Balthael/ciberbal-ai --skill sdd-archive-balthael

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a spec-driven development change is implemented and verified, teams need a consistent way to fold delta specifications back into the source-of-truth specs and preserve the change as an audit trail. This Skill performs that final archival step so completed changes are never lost or left half-merged. ## Core Features & Use Cases - Delta Spec Merging: Applies ADDED, MODIFIED, and REMOVED requirements from delta specs into existing main specs while preserving untouched requirements. - Dated Archiving: Moves the completed change folder into openspec/changes/archive/YYYY-MM-DD-{change-name}/ and verifies all artifacts transferred. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, recording observation IDs for traceability. - Use Case: After a change like 'add-session-expiration' passes verification, the orchestrator launches this Skill to sync the auth spec, archive the change folder, and return a closure summary completing the SDD cycle. ## Quick Start Ask the orchestrator to archive the verified change by name so its delta specs are merged into the main specs and the change folder is moved to the dated archive.

Frequently Asked Questions about sdd-archive

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

FAQPage Schema
How do I archive a completed change in an OpenSpec workflow?

Launch the archive phase after implementation and verification pass. The Skill merges each delta spec into the matching main spec, moves the change folder to openspec/changes/archive/ with a YYYY-MM-DD prefix, and returns a closure summary.

How are delta specs merged into main specs?

Delta sections are applied by type: ADDED requirements are appended, MODIFIED requirements replace matching entries by name, and REMOVED requirements are deleted. Requirements not mentioned in the delta are preserved, and Markdown heading structure is maintained.

What happens if the main spec does not exist yet?

The delta spec is treated as a full spec rather than a delta. It is copied directly from openspec/changes/{change-name}/specs/{domain}/spec.md to openspec/specs/{domain}/spec.md as the new source of truth.

Can a change with critical verification issues be archived?

No. The Skill never archives a change whose verification report contains CRITICAL issues. If a merge would be destructive, such as removing large spec sections, it warns the orchestrator and asks for confirmation first.

What is the difference between engram, openspec, and hybrid modes?

Engram mode stores artifacts only in Engram memory with observation IDs recorded in the archive report. Openspec mode performs filesystem merges and folder moves. Hybrid mode does both, while none mode returns only a closure summary.