sdd-archive

Merge delta specs and verification artifacts into the main spec repository.

Updated Apr 8, 2026

Search Tags:#archive #sdd #openspec #audit-trail #spec-sync #delta-merge #engram

Ready to run

npx skills add https://github.com/aroca89/roca_teams --skill sdd-archive-aroca89

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/aroca89/roca_teams/tree/main/skills/sdd-archive
Command: npx skills add https://github.com/aroca89/roca_teams --skill sdd-archive-aroca89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill closes the SDD loop by merging delta specs, capturing verification artifacts, and creating a traceable archive so completed changes never lose their context.

Core Features & Use Cases

Mode-aware delta sync merges or copies delta specs into the main repository according to the persistence mode while preserving untouched requirements.
Audit-ready reporting records every observation ID and writes an archive report so the orchestrator can trace the artifacts stored in Engram or files.
Filesystem cleanup and verification moves change folders into dated archives when required, confirms all artifacts are present, and ensures the active change directory no longer holds the completed work.

Quick Start

Request the orchestrator to archive the completed change by invoking sdd-archive with the change name and persistence mode.

Frequently Asked Questions about sdd-archive

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

FAQPage Schema

How do I archive SDD delta specifications into the main spec repository?▼

Archiving SDD deltas involves merging or copying delta specs into the main repository according to your persistence mode. The process preserves untouched requirements while moving completed change folders into dated archives, ensuring all verification artifacts are stored and traceable.

What is delta-merge in OpenSpec and how does it preserve existing requirements?▼

Delta-merge is a mode-aware synchronization process that applies new specification changes to the main repository while preserving untouched existing requirements. It ensures completed changes integrate without overwriting unmodified specification sections.

Can I use sdd-archive with hybrid or none persistence modes?▼

Yes, sdd-archive supports engram, openspec, hybrid, and none persistence modes. It applies mode-specific rules for merging deltas and storing artifacts, ensuring completed changes remain traceable across any configured persistence environment.

How do I record observation IDs when finalizing SDD changes?▼

Recording observation IDs during SDD finalization happens automatically when the orchestrator enters the archive phase. It captures every verification observation ID and writes an archive report, ensuring all artifacts stored in Engram or files remain fully traceable.

What happens to change folders after syncing OpenSpec deltas to the audit trail?▼

After syncing OpenSpec deltas, change folders are moved into dated archives within the filesystem. This cleanup confirms all artifacts are present and ensures the active change directory no longer holds completed work.