sdd-archive

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

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/julcasans/atl-lab --skill sdd-archive-julcasans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/julcasans/atl-lab/tree/main/.github/skills/sdd-archive
Command: npx skills add https://github.com/julcasans/atl-lab --skill sdd-archive-julcasans

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of syncing delta specifications into main specs and archiving completed changes, ensuring consistency and proper record-keeping in development workflows.

Core Features & Use Cases

  • Spec Synchronization: Merges delta specs into main specs, handling additions, modifications, and removals of requirements.
  • Change Archiving: Moves completed change folders into archive with date prefixes for audit trails.
  • Use Case: A development team completes feature changes and uses this Skill to update specifications, archive the change, and prepare for subsequent iterations, maintaining organized project documentation.

Quick Start

Use the sdd-archive skill to merge your delta specs into main specs, then archive the change folder for record-keeping.

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 specifications into main project specs?

Delta specifications are merged into main project specs by automatically handling additions, modifications, and removals of requirements. This synchronization ensures the main specification remains an accurate source of truth during software development.

What is the best way to archive completed specification changes for an audit trail?

Archiving completed specification changes involves moving completed change folders into an archive with date prefixes. This maintains an accurate audit trail and ensures proper record-keeping for development workflows.

How does specification merging handle requirement modifications and removals?

Specification merging processes requirement modifications and removals by syncing delta specs into the main specs. It reconciles these changes to maintain specification integrity and traceability across artifacts.

When do I need to archive changes in a specification management workflow?

You need to archive changes when a development team completes feature changes and prepares for subsequent iterations. Archiving moves completed change folders to maintain organized project documentation and an accurate audit trail.

Can I use this spec merging process without external version control dependencies?

Yes, the spec merging and change archiving workflow operates independently without external dependencies. It applies built-in scripts and references to maintain specification integrity and traceability within your development cycle.

Why does syncing delta specs help maintain a source of truth in software development?

Syncing delta specs maintains a source of truth by automatically reconciling feature changes into main specs. This prevents documentation drift and ensures the project specifications accurately reflect completed development work.