skills.rest
AD-Paladins
AD-PaladinsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sdd-archive

Archives completed SDD changes by merging delta specs into main specs.

Updated Jul 10, 2026
Search Tags:#archive#sdd#audit trail#change management#openspec#spec sync#delta specs
One-click install
npx skills add https://github.com/AD-Paladins/beaconator-web --skill sdd-archive-ad-paladins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/AD-Paladins/beaconator-web/tree/main/.config/opencode/skills/sdd-archive
Command: npx skills add https://github.com/AD-Paladins/beaconator-web --skill sdd-archive-ad-paladins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing out a spec-driven development change requires merging delta specifications into the source-of-truth specs and moving the change folder into an audit archive, which is error-prone when done manually. ## Core Features & Use Cases - Delta Spec Sync: Merges ADDED, MODIFIED, REMOVED, and RENAMED requirements from delta specs into main specs while preserving untouched requirements. - Gated Archiving: Blocks archiving when review receipts are missing, tasks remain unchecked, or CRITICAL verification issues exist. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes with a mandatory archive report. - Use Case: After a feature change passes implementation and verification, the orchestrator delegates to this sub-agent to sync specs, move the change folder to openspec/changes/archive/YYYY-MM-DD-{change-name}/, and return a closure summary. ## Quick Start Ask the orchestrator to archive the completed SDD change by delegating to the sdd-archive sub-agent with the change name and artifact store mode.

Frequently Asked Questions about sdd-archive

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

FAQPage Schema
How do I archive a completed SDD change?▼

The orchestrator delegates to the sdd-archive sub-agent with the change name and artifact store mode. The agent syncs delta specs into main specs, moves the change folder to openspec/changes/archive with a date prefix, and persists an archive report.

How does delta spec merging work in OpenSpec archiving?▼

Delta spec sections are matched by requirement name: ADDED requirements are appended, MODIFIED ones replaced, REMOVED ones deleted after recording Reason and Migration notes, and RENAMED ones renamed while preserving scenarios. Requirements not in the delta are preserved.

Can I archive a change with unchecked tasks in tasks.md?▼

No, unchecked implementation tasks block archiving by default. Only if the orchestrator explicitly approves reconciliation and apply-progress plus verify-report prove completion can stale checkboxes be repaired, with the reason recorded in the archive report.

What blocks the SDD archive process?▼

Archiving is blocked by missing or invalid review gate receipts, CRITICAL issues in the verify-report, unchecked tasks without proof of completion, and workspace-planning action contexts. CRITICAL verification issues have no override.

Does sdd-archive work without an openspec directory?▼

Yes, in engram mode artifacts live in Engram only and the archive report records observation IDs instead of filesystem moves. In none mode it returns a closure summary without any file operations.

Related Skills

Explore More Software Engineering Skills→
Gentleman-ProgrammingGentleman-Programming
6.1k

sdd-onboard

Guides users through a complete Spec-Driven Development cycle on their real codebase.

Official
Advanced
RamonsDkaRamonsDka
1

sdd-archive

Merge delta specs into main specs and archive change folders.

Community
Advanced
etrigan16etrigan16

sdd-archive

Archives completed SDD changes by merging delta specs into main specs.

Community
Advanced
sap-tutorialssap-tutorials
7

openspec-archive-change

Archives completed OpenSpec changes with artifact, task, and spec sync verification.

Official
Intermediate