sdd-archive

Automate SDD cycle closure by merging delta specifications into main project specifications.

Updated May 9, 2026
One-click install
npx skills add https://github.com/LeandroBenjaminL/lend-ai --skill sdd-archive-leandrobenjaminl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/LeandroBenjaminL/lend-ai/tree/main/skills/sdd-archive
Command: npx skills add https://github.com/LeandroBenjaminL/lend-ai --skill sdd-archive-leandrobenjaminl

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill addresses the challenge of manually closing Software Design Description (SDD) cycles by automating the synchronization of delta specifications to main specifications, merging changes, updating documentation, and persisting the final state.

Core Features & Use Cases

  • Automate SDD Closure: Automates the closing of SDD changes, reducing manual effort and potential errors.
  • Spec Synchronization: Ensures delta specifications are correctly integrated into the main project specifications.
  • Documentation Update: Keeps documentation up to date with the merged changes, providing traceability and future reference.
  • Use Case: Perfect for teams that require automated closure of SDD changes to maintain accurate project specifications and ensure smooth project flow.

Quick Start

After an SDD verify step passes, execute the 'sdd-archive' skill to close the SDD cycle and persist the final state.

Frequently Asked Questions about sdd-archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate SDD cycle closure and sync delta specifications?

Automate SDD cycle closure by integrating delta specifications with main project specifications, merging changes, and updating documentation. This skill executes after an SDD verify step passes to persist the final state.

What is the best way to merge changes and update documentation after SDD verification?

Merging changes and updating documentation during SDD closure is handled by synchronizing delta specifications to main project specifications. This ensures accurate project specs and traceability after changes are merged.

Do I need issue tracking systems and spec repositories to automate SDD closure?

Yes, automating SDD closure requires access to change artifacts, spec repositories, and issue tracking systems. These inputs ensure delta specifications integrate correctly into your main project specifications.

Can I use automated documentation updates for SDD methodology in software engineering?

Automated documentation updates for SDD methodology keep your specs aligned with merged changes. This provides traceability and future reference by syncing delta specifications directly into main project specifications.

When should I run an SDD archive step in my software development workflow?

Run the SDD archive step immediately after your SDD verify step passes. This closes the SDD cycle, merges changes, updates documentation, and persists the final state of your project specifications.

Why does manual SDD closure introduce errors in change management?

Manual SDD closure introduces errors because synchronizing delta specifications to main specs and updating documentation by hand is prone to mistakes. Automating this closure reduces manual effort and ensures spec accuracy.