skills.rest
JNZader
JNZaderCOMMUNITY
Explore all skills by this author →
GitHub

sdd-archive

Merge delta specs into main specs and archive changes with dated reports.

Updated Mar 15, 2026
Search Tags:#workflow#audit#merge#archive#traceability#delta#specs
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill sdd-archive-jnzader
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/JNZader/javi-ai/tree/main/delta/overrides/sdd-archive
Command: npx skills add https://github.com/JNZader/javi-ai --skill sdd-archive-jnzader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs into the main specs repository and archive completed changes to preserve traceability and prevent drift.

Core Features & Use Cases

  • Merge delta specifications into the canonical main specs with conflict-aware resolution.
  • Move the entire change folder to a dated archive path openspec/changes/archive/YYYY-MM-DD-{change-name}/.
  • Persist an archive report to the configured backends (Engram/Openspec) per mode to maintain an audit trail.
  • Provide verification steps and an auditable summary of the archive.

Quick Start

Archive a completed delta change by triggering the orchestrator workflow to merge specs and move the change to archive.

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 a main specs repository without losing traceability?▼

To merge delta specs without losing traceability, archive the completed delta changes into the main specs repository using conflict-aware resolution. This process syncs specifications while moving the change folder to a dated archive path to preserve audit trails.

What is the best way to archive delta changes and prevent spec drift?▼

Archiving delta changes prevents spec drift by moving completed change folders to a dated archive path and persisting an archive report. This maintains an auditable summary and ensures the main specs repository stays canonical and synchronized.

Does the archiving process support both delta-merge and full-replace scenarios?▼

Yes, the archiving process supports both delta-merge and full-replace scenarios across domains. It applies mode-aware behavior to satisfy specific merge rules, ensuring the archive report persistence adapts to the chosen replacement strategy.

How do I relocate archived specifications using a date-prefix directory structure?▼

You relocate archived specifications by moving the entire change folder to a date-prefix directory structure at openspec/changes/archive/YYYY-MM-DD-{change-name}/. This ensures chronological organization and traceable audit trails for completed work.

Can I persist an archive report to Engram or Openspec backends for auditing?▼

Yes, you can persist an archive report to Engram or Openspec backends for auditing. The archiving workflow operates with mode-aware behavior to generate and store these reports, maintaining a verifiable audit trail across configured systems.

Related Skills

Explore More Software Engineering Skills→
RamonsDkaRamonsDka
1

sdd-archive

Merge delta specs into main specs and archive change folders.

Community
Advanced
RyanCallahan312RyanCallahan312

openspec-archive-change

Archive completed OpenSpec changes to an auditable directory with metadata.

Community
Advanced
nullmastermindnullmastermind
9

spx-archive

Archive completed openspec changes with status checks and delta-spec syncing.

Community
Advanced
dallaydallay

sdd-archive

Merge delta specifications into main specs and archive completed changes.

Official
Intermediate