skills.rest
maxculen86
maxculen86COMMUNITY
Explore all skills by this author →
GitHub

sdd-archive

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

Updated Apr 1, 2026
Search Tags:#workflow#merge#spec#archive#sdd#openspec
One-click install
npx skills add https://github.com/maxculen86/coding-bro-ai --skill sdd-archive-maxculen86
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/maxculen86/coding-bro-ai/tree/main/internal/assets/skills/sdd-archive
Command: npx skills add https://github.com/maxculen86/coding-bro-ai --skill sdd-archive-maxculen86

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs to the main specs (source of truth) and archive completed changes after verification, providing an auditable trail of the SDD cycle.

Core Features & Use Cases

  • Merge delta specs into main specs by applying added, modified, and removed sections while preserving unrelated content.
  • Move completed change folders into an archive with date-prefixes for traceability and compliance.
  • Enforce an audit-friendly workflow across multiple modes (engram, openspec, hybrid) with mandatory archive reporting.

Quick Start

After implementing a change, run the sdd-archive skill to merge the delta into the main spec and archive the change for future reference.

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 the main spec after completing changes?▼

To merge delta specs into the main spec, apply the added, modified, and removed sections from the delta while preserving unrelated content in the main spec. This process syncs the source of truth and archives completed changes for compliance.

How does spec archiving work in an SDD workflow?▼

Spec archiving works by moving completed change folders into an archive with date-prefixes for traceability. This mechanism enforces an audit-friendly workflow across engram, openspec, and hybrid modes while generating a mandatory archive report.

When do I need to archive delta specs in spec-driven development?▼

You need to archive delta specs in spec-driven development after implementing and verifying a change. This step syncs the delta to the main spec, providing an auditable trail of the SDD cycle and ensuring compliance.

Can I use openspec and hybrid modes when archiving specs?▼

Yes, you can use openspec and hybrid modes when archiving specs. The archive process supports engram, openspec, and hybrid modes, enforcing an audit-friendly workflow with mandatory archive reporting across all supported environments.

What is the best way to preserve unrelated content when merging specs?▼

The best way to preserve unrelated content when merging specs is to apply only the added, modified, and removed sections from the delta spec. This targeted merge maintains the integrity of the main spec while archiving completed changes.

Why does spec archiving generate an archive report?▼

Spec archiving generates an archive report to enforce an audit-friendly workflow and provide a compliance trail. This report documents the merged changes and the archived folders, ensuring traceability throughout the SDD cycle.

Related Skills

Explore More Software Engineering Skills→
alexei-lexxalexei-lexx

openspec-verify-change

Validate alignment between openspec change artifacts and implemented code.

Community
Advanced
patornpatorn

openspec-archive-change

Archive completed OpenSpec changes with date-stamped folders and status checks.

Community
Intermediate
danielsogldanielsogl
39

openspec-archive-change

Archive completed OpenSpec changes after validating delta-spec synchronization.

Community
Advanced
dallaydallay

sdd-archive

Merge delta specifications into main specs and archive completed changes.

Official
Intermediate