sdd-archive

Merge delta specs into main documentation and record archival state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill closes changes by consolidating delta specs into the main documentation and persisting the final state, ensuring a formal archive of completed work.

Core Features & Use Cases

  • Merges delta specs into the main docs and creates an Archive record to preserve the final state.
  • Pre-archive validation to ensure all tasks are complete and verification has passed before archiving.
  • Audit trail & artifacts generation that references explore/spec/tasks/apply/verify outputs for traceability.

Quick Start

Archive the change after verification passes and all tasks are complete by merging delta specs into main documentation and generating a formal archive record.

Frequently Asked Questions about sdd-archive

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

FAQPage Schema
How do I archive documentation changes by merging delta specs?

To archive documentation changes, merge delta specs into the main documentation and generate a formal archive record. This process persists the final state and records timeline, artifacts, and summary for complete traceability.

What is spec-merge based change archiving in software engineering?

Spec-merge archiving is a change-management process that consolidates delta specs into main documentation. It ensures a formal archive of completed work by persisting the final state and preserving the consolidated documentation.

Can I archive changes before task completion and verification pass?

No, you cannot archive changes before verification passes. Pre-archive validation enforces prerequisites by validating task completion and verification results, ensuring only fully verified changes are merged into the main documentation.

How do I create an audit trail for archived change management artifacts?

Create an audit trail by generating an archive entry that references explore, spec, tasks, apply, and verify outputs. This records the timeline, artifacts, and summary to ensure full traceability of the completed change.