sdd-archive

Merge delta specs into main specs and archive change folders.

1|1|Updated Apr 19, 2026

Search Tags:#archive #sdd #openspec #version-control #spec-merge #engram

Ready to run

npx skills add https://github.com/RamonsDka/the-architect-overlay --skill sdd-archive-ramonsdka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/sdd-archive
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill sdd-archive-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end SDD archiving workflow by merging delta specs into the main specs (source of truth) and moving the completed change folder into the archive, ensuring an auditable trail.

Core Features & Use Cases

Merge delta specs into main specs when an updated domain is released, preserving unrelated requirements to maintain integrity.
Move change folders to archive with date-prefixed paths to maintain a clear history of iterations and deployments.
Generate and persist a comprehensive archive report that records observation IDs and traceability data across Engram/Openspec workflows.

Quick Start

Provide the change name and target workspace to initiate the archival workflow.

Frequently Asked Questions about sdd-archive

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

FAQPage Schema

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

To merge delta specs into main specs automatically, you initiate the archival workflow by providing the change name and target workspace. The process enforces update rules and validates main spec existence to preserve unrelated requirements.

What is the SDD archiving workflow for completed changes?▼

The SDD archiving workflow is an automated process that merges delta specs into the source of truth and moves completed change folders into a date-prefixed archive. It generates a comprehensive archive report to ensure traceability and maintain a clear history.

Does spec merging work with both engram and openspec mode configurations?▼

Yes, spec merging works across engram, openspec, hybrid, and none mode configurations. The process operates across these specific configurations to merge delta specs where applicable and manage filesystem archive actions accordingly.

How do I archive completed change folders with date-prefixed paths?▼

You archive completed change folders with date-prefixed paths by running the end-to-end archival workflow. This moves the completed change folder into the archive, maintaining a clear history of iterations and deployments for auditable tracking.

Can I archive partial delta specs without losing unrelated requirements?▼

Yes, you can archive partial or full delta specs without losing unrelated requirements. The merge process enforces update rules that preserve unrelated requirements in the main specs to maintain overall system integrity during the archival.

How does the archive report record observation IDs and traceability data?▼

The archive report records observation IDs and traceability data by generating and persisting a comprehensive log after the merge and move operations. This ensures auditable tracking across engram and openspec workflows during the archival process.