sdd-archive

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

1|Updated Dec 30, 2025

Search Tags:#documentation #version control #workflow automation #specification #archive #sdd

Ready to run

npx skills add https://github.com/statick88/dotfiles --skill sdd-archive-statick88

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the final steps of the SDD cycle by merging implemented changes into the main specifications and archiving the completed work, ensuring a clean and traceable project history.

Core Features & Use Cases

Spec Synchronization: Merges delta specifications into the main source of truth, handling both new and updated specs.
Automated Archiving: Moves completed change folders to a dated archive, maintaining an audit trail.
Verification: Confirms that main specs are updated and the change is correctly archived.
Use Case: After a feature is developed and verified, this Skill ensures its specifications are integrated into the master documentation and the development artifacts are stored for future reference.

Quick Start

Archive the change named 'user-authentication-flow' after its implementation and 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 completed software development documentation changes?▼

You can archive software development documentation changes by merging delta specifications into main specs and moving the change folder to a dated archive folder. This automates the final steps of the SDD cycle, ensuring a clean and traceable project history.

What is the best way to merge delta specifications into main source of truth?▼

The best way to merge delta specifications is through spec synchronization, which integrates implemented changes into the main source of truth. It handles both new and updated specs, ensuring the master documentation reflects the latest verified features.

When do I need to archive completed SDD changes?▼

You need to archive completed SDD changes after a feature is developed and verified. This ensures its specifications are integrated into the master documentation and the development artifacts are stored for future reference, maintaining an audit trail.

How does automated archiving verify that main specs are updated?▼

Automated archiving verifies updated specs by confirming that main specifications are correctly merged and the change is correctly archived. It checks the dated archive folder to ensure complete traceability of the development artifacts.

Can I use this SDD archiving workflow without any external dependencies?▼

Yes, you can use this SDD archiving workflow without external dependencies. The Skill operates independently using its internal scripts and references to automate the merging and archiving process.

Does this archiving process move the entire change folder to a dated archive?▼

Yes, the archiving process moves the completed change folder to a dated archive. This maintains an audit trail by storing development artifacts with timestamps for future reference and traceability.