sdd-archive

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

Updated Feb 12, 2026

Search Tags:#workflow #merge #archive #openspec #delta #specs #change-management

Ready to run

npx skills add https://github.com/tiagofur/kakoclaw --skill sdd-archive-tiagofur

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/tiagofur/kakoclaw/tree/main/.claude/skills/sdd-archive
Command: npx skills add https://github.com/tiagofur/kakoclaw --skill sdd-archive-tiagofur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs to main specs and archive a completed change. Trigger: When the orchestrator launches you to archive a change after implementation and verification.

Core Features & Use Cases

Merge delta specs into the main specs (openspec/specs/{domain}/spec.md) by applying added, modified, and removed requirements while preserving others.
Move the delta change folder to an archive path openspec/changes/archive/YYYY-MM-DD-{change-name}/ and keep an auditable trail.
Ensure the source of truth is updated and verifiable, with an archive that supports traceability and rollback if needed.

Quick Start

Trigger the OpenSpec archive workflow for a completed delta change after successful verification.

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 after merging changes into main specs?▼

To archive delta specs, you sync the delta changes into the main specs by applying added, modified, and removed requirements, then move the completed change folder to a dated archive path. This preserves unchanged requirements and updates the source of truth.

What is the OpenSpec archive workflow for completed change management?▼

The OpenSpec archive workflow synchronizes completed delta specs into main specs, enforcing artifact_store mode logic. It moves the finished change folder to an archive path with an ISO date, ensuring the source of truth is updated and verifiable.

How does merging delta specs preserve existing requirements in the source of truth?▼

Merging delta specs applies only the added, modified, and removed requirements to the main specs. It explicitly preserves all unchanged requirements within the source of truth, ensuring only verified changes are integrated during the archive process.

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

You move a completed change folder to an archive path immediately after implementation and successful verification. The orchestrator triggers this archiving step to create an auditable trail with an ISO date for traceability and potential rollback.

Does the archive process support rollback for merged delta specs?▼

Yes, the archive process supports rollback by moving completed delta change folders to a dated archive path. This creates an auditable trail that preserves the change history alongside the updated source of truth for recovery if needed.