skills.rest
dallay
dallayOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sdd-archive

Merge delta specifications into main specs and archive completed changes.

Updated Apr 14, 2026
Search Tags:#workflow#merge#archive#delta#specs#audit-trail
One-click install
npx skills add https://github.com/dallay/opencode-docker --skill sdd-archive-dallay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/sdd/sdd-archive
Command: npx skills add https://github.com/dallay/opencode-docker --skill sdd-archive-dallay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncing delta specs into the main source of truth after change implementation and verification, then archiving the completed change.

Core Features & Use Cases

  • Merge delta specs into main specs when changes are verified
  • Move the entire change folder to an archive path with an ISO date prefix
  • Maintain an auditable trail of spec updates and archival actions

Quick Start

Initiate the sdd-archive workflow after verification to merge delta specs into main specs and archive the change.

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 after implementation?▼

To merge delta specs into main specs, initiate the archive workflow after change verification. It consolidates delta specifications into the main source of truth and moves the completed change folder to an archive directory.

When should I archive completed delta specifications?▼

You should archive completed delta specifications after implementation and verification are complete. This ensures the main specs reflect the latest verified changes and maintains an auditable trail of spec updates.

What is the best way to maintain an audit trail for archived spec changes?▼

The best way to maintain an audit trail for archived spec changes is to move completed change folders to an archive path with an ISO date prefix. This enforces archive relocation and audit-trail integrity.

How does the spec archival process enforce merge rules?▼

The spec archival process enforces merge rules by syncing delta specs into the main source of truth only after verification. It then relocates the entire change folder to ensure traceability and consistency.

Can I use this archival workflow across different project domains?▼

Yes, you can use this archival workflow across different project domains. It applies universally to consolidate changes after implementation and verification, ensuring traceability with ISO-date archive prefixes.

Why does the archive workflow use ISO date prefixes for change folders?▼

The archive workflow uses ISO date prefixes for change folders to ensure traceability and maintain audit-trail integrity. This naming convention organizes archived changes chronologically within the archive directory.

Related Skills

Explore More Software Engineering Skills→
EduardoJVNEduardoJVN

sdd-archive

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

Community
Advanced
StrocsStrocs

sdd-archive

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

Community
Advanced
bacocobacoco
67

openspec-change-closure

Archive completed OpenSpec changes by merging delta specs into living specifications.

Community
Advanced
julcasansjulcasans

sdd-archive

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

Community
Intermediate