sdd-archive

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

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill sdd-archive-juanjo-zurich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/juanjo-zurich/juarvis-v4/tree/main/plugins/sdd/skills/sdd-archive
Command: npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill sdd-archive-juanjo-zurich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a change is implemented and verified in a Spec-Driven Development workflow, its delta specs and artifacts remain scattered in a working folder. This Skill completes the SDD cycle by merging delta specs into the main source-of-truth specs and moving the change folder into a dated archive, preserving a full audit trail. ## 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 to openspec/changes/archive/YYYY-MM-DD-{change-name}/ with verification of archive contents. - Multi-Backend Persistence: Supports engram (memory-based), openspec (filesystem), hybrid, and none artifact store modes, recording observation IDs for traceability. - Use Case: After the verification sub-agent approves a change, the orchestrator launches this Skill to sync the new requirements into openspec/specs/, archive the change folder, and return a structured closure summary. ## Quick Start Archive the completed change 'add-user-auth' by syncing its delta specs into the main specs and moving it to the dated archive folder.

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 SDD workflow?▼

Sync each delta spec into the main specs under openspec/specs/, then move the change folder to openspec/changes/archive/ with a YYYY-MM-DD date prefix. Verify the archive contents and return a structured closure summary to the orchestrator.

How do I merge delta specs into existing main specs?▼

Match requirements by name and apply the delta operations: append ADDED requirements, replace MODIFIED ones, and delete REMOVED ones. Preserve all requirements not mentioned in the delta and maintain Markdown heading hierarchy.

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

Engram mode stores artifacts only in persistent memory via mem_save and skips filesystem operations. Openspec mode performs filesystem merges and folder moves only. Hybrid mode does both, writing the archive report to memory and moving files on disk.

Why does archiving fail when using mem_search results directly?▼

mem_search returns only 300-character previews, not full content. You must call mem_get_observation with each returned ID to retrieve complete artifacts before archiving, otherwise the archive report will contain incomplete data.

When should a change not be archived?▼

Never archive a change whose verification report contains CRITICAL issues. Also warn the orchestrator and request confirmation if the spec merge would be destructive, such as removing large sections of an existing spec.