skills.rest
adacosdev
adacosdevCOMMUNITY
Explore all skills by this author →
Website𝕏@aacosa34GitHub

sdd-archive

Merge delta specs into main specifications and archive completed change folders.

Updated Feb 1, 2026
Search Tags:#archive#openspec#audit-trail#change-management#delta-spec#spec-merge#engram
One-click install
npx skills add https://github.com/adacosdev/dotfiles --skill sdd-archive-adacosdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/adacosdev/dotfiles/tree/main/dot_config/opencode/skills/sdd-archive
Command: npx skills add https://github.com/adacosdev/dotfiles --skill sdd-archive-adacosdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive delta specs by merging them into the main specification source of truth and moving the completed change folder to an auditable archive with traceable provenance.

Core Features & Use Cases

  • Merge delta specs into the main specs to keep the source of truth up to date.
  • Move the completed change folder to a date-prefixed archive directory for provenance.
  • Generate and store an archive report that captures artifact IDs and actions for auditability.

Quick Start

Instruct the orchestrator to archive a completed change by triggering the sdd-archive workflow.

Frequently Asked Questions about sdd-archive

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

FAQPage Schema
How do I archive delta specs and merge them into the main specifications?▼

To archive delta specs, merge them into the main specifications and move the completed change folder to a date-prefixed archive directory. This process preserves existing non-delta data and outputs a structured summary including archive path and verification status.

What is the best way to maintain an audit trail for completed change management?▼

Maintaining an audit trail for change management involves moving completed change folders to an archive directory and generating a report capturing artifact IDs and actions. This ensures traceable provenance and auditability for merged delta specs.

Does spec merging overwrite existing data in the main specifications?▼

Spec merging enforces non-destructive merges, preserving existing non-delta data in the main specifications. Only the completed delta spec changes are integrated, ensuring the source of truth remains intact while updating with new artifacts.

Can I use OpenSpec and Engram modes for archiving delta specs?▼

Yes, archiving delta specs operates across engram, openspec, and hybrid modes. Each mode applies explicit rules for artifact handling and filesystem moves to successfully archive folders and generate verification reports.

What is included in the archive report after merging delta specs?▼

The archive report includes artifact IDs, executed actions, archive path, updated specs, and verification status. This structured summary provides full auditability and traceable provenance for the completed change management process.

When should I move a completed change folder to an archive directory?▼

You should move a completed change folder to an archive directory after successfully merging its delta specs into the main specifications. This finalizes the change management workflow by securing the provenance and generating the audit report.

Related Skills

Explore More Software Engineering Skills→
EduardoJVNEduardoJVN

sdd-archive

Merge delta specifications into main specifications and archive completed change folders.

Community
Advanced
zMynxxzMynxx

sdd-archive

Merge completed delta specifications and preserve audit trails for archived SDD changes.

Community
Advanced
StrocsStrocs

sdd-archive

Merge delta specs into main specs and archive implemented change folders.

Community
Advanced
yakksiekyakksiek

10x-archive

Move completed change folders to an archive directory and update related documents.

Community
Advanced