skills.rest
EduardoJVN
EduardoJVNCOMMUNITY
Explore all skills by this author →
GitHub

sdd-archive

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

Updated Mar 9, 2026
Search Tags:#documentation#version control#specification#sync#archive#sdd
One-click install
npx skills add https://github.com/EduardoJVN/my-ia-config --skill sdd-archive-eduardojvn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/EduardoJVN/my-ia-config/tree/main/.claude/skills/sdd-archive
Command: npx skills add https://github.com/EduardoJVN/my-ia-config --skill sdd-archive-eduardojvn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the final steps of the SDD cycle by merging specification changes into the main source of truth and archiving completed work, ensuring a clean and organized project history.

Core Features & Use Cases

  • Spec Synchronization: Merges delta specifications into main specifications, handling additions, modifications, and deletions of requirements.
  • Automated Archiving: Moves completed change folders to a dated archive, preserving project history.
  • Verification: Ensures changes are ready for archiving by checking verification reports.
  • Use Case: After a feature is implemented and verified, this Skill can be triggered to update the main documentation and move the associated development artifacts to a permanent archive.

Quick Start

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

Frequently Asked Questions about sdd-archive

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

FAQPage Schema
How do I sync delta specifications into main specifications after completing development?▼

You archive completed changes by triggering the sdd-archive process with the specific change name, which merges delta specifications into the main source of truth and moves the associated change folder to a dated archive.

What is the best way to archive completed development changes and maintain an audit trail?▼

The best way to archive completed development changes is using an automated synchronization tool that merges delta specifications into the main source of truth and moves change folders to a dated archive, ensuring a clean project history and audit trail.

Can I archive project artifacts without checking verification reports first?▼

No, you should not archive project artifacts without checking verification reports first, as the archiving process verifies that changes are ready by reviewing these reports before moving folders to a dated archive.

Does the specification synchronization process handle requirement deletions and modifications?▼

Yes, specification synchronization handles requirement deletions and modifications, along with additions, by merging delta specifications into the main source of truth to maintain accurate project documentation.

When do I need to archive completed changes in the SDD cycle?▼

You need to archive completed changes in the SDD cycle after a feature is implemented and verified, which ensures the main documentation is updated and the SDD cycle reaches completion with a preserved audit trail.

Related Skills

Explore More Software Engineering Skills→
SAPSAP
221

openspec-sync-specs

Merge delta specifications into main OpenSpec specs under openspec/specs.

Official
Advanced
dallaydallay

sdd-archive

Merge delta specifications into main specs and archive completed changes.

Official
Intermediate
fkoschifkoschi
2

openspec-sync-specs

Merge delta specification changes into main specification files for the openspec CLI.

Community
Advanced
arestivoarestivo

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes while resolving delta-spec conflicts.

Community
Advanced