sdd-archive

Name: sdd-archive
Availability: InStock
Author: thiagoooo34252

Automates SDD change archiving by syncing delta specs, moving folders, and generating a summary report.

1|Updated Apr 12, 2026

Search Tags:#SDD #change management #engineering workflow #Spec-Driven Development #specification archiving

Ready to run

npx skills add https://github.com/thiagoooo34252/atlas-engineer --skill sdd-archive-thiagoooo34252

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the archiving of completed SDD changes, ensuring that specifications are synchronized and changes are properly documented.

Core Features & Use Cases

Spec Synchronization: Merges delta specifications into the main specifications.
Change Archiving: Moves completed change folders to an archive location.
Verification: Confirms the accuracy of the archive and completeness of the SDD cycle.
Reporting: Generates a summary report of the archived change.
Use Case: Ideal for engineering teams following Spec-Driven Development to streamline the process of archiving completed changes and maintaining a clean and organized project history.

Quick Start

Archive the change with the name 'feature-x' by running the command 'archive-change feature-x'.

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 Spec-Driven Development changes automatically?▼

You can automate Spec-Driven Development archiving by running a command like 'archive-change feature-x', which synchronizes delta specifications, moves change folders to the archive, and generates a summary report.

What does spec synchronization do when archiving SDD changes?▼

Spec synchronization merges delta specifications into the main specifications during archiving, ensuring your project history remains accurate and the primary specification documents reflect all completed modifications.

Do I need orchestrator system permissions to archive SDD changes?▼

Yes, archiving SDD changes requires access to SDD change artifacts and orchestrator system permissions to successfully move completed change folders and verify the accuracy of the archive.

Can I generate a summary report for an archived engineering workflow change?▼

Yes, the archiving process generates a summary report detailing the archived change, providing engineering teams with documentation of the completed SDD cycle and synchronized specifications.

What is the best way to maintain a clean project history after Spec-Driven Development?▼

The best way to maintain a clean project history is to move completed change folders to an archive location after synchronizing delta specifications, verifying archive accuracy, and generating a summary report.

Why does my SDD change archiving process require verification?▼

Verification confirms the accuracy of the archive and the completeness of the SDD cycle, ensuring delta specifications are properly merged and change folders are correctly moved before finalizing.