skills.rest
Alan-TheGentleman
Alan-TheGentlemanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sdd-archive

Merge delta specs into main specs and archive completed changes.

10|Updated Feb 28, 2026
Search Tags:#workflow#audit#spec#archive#sdd#openspec#engram
One-click install
npx skills add https://github.com/Alan-TheGentleman/gentle-ai-enterprise --skill sdd-archive-alan-thegentleman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/Alan-TheGentleman/gentle-ai-enterprise/tree/main/skills/sdd-archive
Command: npx skills add https://github.com/Alan-TheGentleman/gentle-ai-enterprise --skill sdd-archive-alan-thegentleman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the safe alignment of delta specifications with the main source of truth by merging changes and moving completed work into the archive, ensuring traceability across the SDD cycle.

Core Features & Use Cases

  • Merges delta specs into main specs when a main spec exists; if the main spec does not exist, the delta spec becomes the main spec.
  • Archives the completed change folder under openspec/changes/archive with an ISO date prefix to preserve an auditable trail.
  • Provides an audit-friendly summary and enforces the defined archive rules to ensure traceability and compliance.

Quick Start

Trigger the archive workflow for a completed change and let the agent merge delta specs into main specs before moving the change folder to the 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 main specs in an OpenSpec workflow?▼

To archive delta specs, the workflow merges completed changes into the main source of truth. If a main spec exists, the delta merges into it; if not, the delta automatically becomes the main spec.

What is the best way to archive completed change folders in OpenSpec?▼

The best way to archive completed changes is moving them under openspec/changes/archive with an ISO date prefix. This preserves an auditable trail and enforces traceable archive integrity checks across the SDD cycle.

When do I need to archive delta specifications during spec-driven development?▼

You need to archive delta specifications when a change is completed and ready for the main specs. Archiving relocates the change folder to maintain an audit-friendly history and ensure compliance with SDD rules.

Does the OpenSpec archive process generate an audit summary for completed changes?▼

Yes, the archive process generates an audit-friendly summary. It enforces defined archive rules and automated merge checks to ensure traceability and compliance for merged delta specs.

Can I use automated merge rules to sync delta specs without losing main spec data?▼

Yes, automated merge rules safely sync delta specs. The workflow applies verification and archive integrity checks to align delta changes with the main specs without losing existing source of truth data.

Why does my completed change folder need an ISO date prefix in the archive?▼

An ISO date prefix preserves an auditable trail for completed changes. This chronological naming enforces traceable history requirements and ensures archive integrity across the SDD cycle.

Related Skills

Explore More Software Engineering Skills→
remiverdiesenremiverdiesen
6

openspec-bulk-archive-change

Archive completed OpenSpec changes into the archive directory.

Community
Advanced
cookeyholdercookeyholder

openspec-sync-specs

Merge delta specifications into main specs with conflict resolution and change summaries.

Community
Advanced
sebasmzgsebasmzg

sdd-archive

Merge delta specs into main specifications and archive change folders.

Community
Advanced
julcasansjulcasans

sdd-archive

Merge delta specifications into main project specs and archive completed changes.

Community
Intermediate