sdd-archive

Name: sdd-archive
Availability: InStock
Author: Gentleman-Programming

Merge delta specs into main specs and archive completed changes.

1.3k|159|Updated Feb 16, 2026

Search Tags:#audit #merge #archive #openspec #delta #specs

Ready to run

npx skills add https://github.com/Gentleman-Programming/agent-teams-lite --skill sdd-archive-gentleman-programming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/Gentleman-Programming/agent-teams-lite/tree/main/skills/sdd-archive
Command: npx skills add https://github.com/Gentleman-Programming/agent-teams-lite --skill sdd-archive-gentleman-programming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specifications often live in a staging area and must be merged into the main specifications before archiving. This skill ensures the source of truth stays up to date and archived changes are traceable.

Core Features & Use Cases

Delta-main merge: Merges delta specs from openspec/changes/{change-name}/specs into the main spec when the main exists, or copies the delta as the main spec when it does not.
Archive workflow: Moves the complete change folder to an ISO-date prefixed archive path and preserves an auditable trail.
Verification & auditing: Validates that the main specs reflect the delta and that the archive contains proposals, designs, specs, and tasks as artifacts.

Quick Start

Trigger the sdd-archive sub-agent after delta specs are ready under openspec/changes/{change-name}/specs and the orchestrator signals archiving.

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 before archiving?▼

To merge delta specs into main specs, the skill merges changes from openspec/changes/{change-name}/specs into the existing openspec/specs/{domain}/spec.md file. If no main spec exists, it copies the delta spec to serve as the new main spec.

What is an openspec archive workflow for completed changes?▼

An openspec archive workflow moves the completed change folder to an ISO-date prefixed archive path. This preserves an auditable trail of proposals, designs, specs, and tasks after the delta specs are merged into main specs.

Do I need an existing main spec to archive a delta spec?▼

No, you do not need an existing main spec to archive a delta spec. The workflow copies the delta spec as the main spec when it does not exist, or merges into it when it does, before moving the change to the archive path.

How does the archive process verify auditable spec artifacts?▼

The archive process verifies auditable spec artifacts by validating that main specs reflect the merged delta and confirming the archive folder contains proposals, designs, specs, and tasks, returning a summary with artifact observations.

What is the best way to keep openspec delta specs synchronized with main specs?▼

The best way to synchronize openspec delta specs with main specs is to trigger the archive workflow. It merges the delta specifications into the main source of truth and moves the completed change folder to a date-prefixed archive path.