sdd-archive

Merge delta specifications into main specs and archive completed changes.

1|1|Updated Jul 31, 2025

Search Tags:#documentation #version control #specification #sync #archive #sdd

Ready to run

npx skills add https://github.com/JoaquinFontaana/alquileres --skill sdd-archive-joaquinfontaana

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/JoaquinFontaana/alquileres/tree/main/.agents/skills/sdd-archive
Command: npx skills add https://github.com/JoaquinFontaana/alquileres --skill sdd-archive-joaquinfontaana

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the final steps of the Software Development Description (SDD) cycle by merging updated specifications into the main source of truth and archiving completed work, ensuring a clean and auditable project history.

Core Features & Use Cases

Spec Synchronization: Merges delta specifications into main specifications, handling both new and updated specs.
Automated Archiving: Moves completed change folders to a dated archive, maintaining a historical record.
Use Case: After a feature has been implemented and verified, this Skill ensures its specifications are integrated into the main documentation and the change is moved to a permanent archive, ready for the next iteration.

Quick Start

Use the sdd-archive skill to archive the change named 'user-authentication-flow'.

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 specifications and sync delta changes?▼

To archive completed software specifications and sync delta changes, merge updated delta specifications into main spec files and move completed change directories to a dated archive folder.

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

Merging delta specifications into main source of truth documentation involves synchronizing new and updated requirements into the primary spec files, ensuring a clean and auditable project history before archiving.

When do I need to archive changes in the software development lifecycle?▼

You need to archive changes in the software development lifecycle after a feature has been implemented and verified, ensuring its specifications are integrated and the change is moved to a permanent record.

How does automated spec synchronization handle updated vs new spec files?▼

Automated spec synchronization handles updated and new spec files by merging delta specifications into the main specifications, carefully managing spec versions and adhering to archiving rules.

Can I use this archival process to maintain a dated historical record of project changes?▼

Yes, you can use this archival process to maintain a dated historical record by moving completed change folders to a dated archive, ensuring a permanent and auditable history of integrated specifications.

What are the limitations when synchronizing specifications and archiving completed work?▼

Limitations when synchronizing specifications and archiving completed work include the requirement for careful handling of spec versions and strict adherence to archiving rules to avoid corrupting the main source of truth.