skills.rest
albersg
albersgCOMMUNITY
Explore all skills by this author →
GitHub

sdd-archive

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

Updated Mar 7, 2026
Search Tags:#archive#sdd#audit trail#openspec#spec-driven-development#sub-agent#delta specs
One-click install
npx skills add https://github.com/albersg/dotfiles --skill sdd-archive-albersg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/albersg/dotfiles/tree/main/dotfiles-opencode/.opencode/skills/sdd-archive
Command: npx skills add https://github.com/albersg/dotfiles --skill sdd-archive-albersg

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 and risks stale task states or unverified work being recorded as complete. ## Core Features & Use Cases - Delta Spec Sync: Merges ADDED, MODIFIED, REMOVED, and RENAMED requirements from delta specs into main specs while preserving untouched requirements. - Gate Enforcement: Blocks archiving when the native review receipt is missing, tasks remain unchecked, or CRITICAL verification issues exist. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, persisting an archive report with observation IDs for traceability. - Use Case: After an SDD 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 produce a final-state archive report. ## 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 YYYY-MM-DD prefix, and persists an archive report.

What blocks an SDD change from being archived?▼

Archive is blocked by a missing or invalid native review receipt, unchecked implementation tasks in the persisted tasks artifact, or CRITICAL issues in the verify report. CRITICAL issues have no override and require re-running verification.

How does delta spec merging work in openspec?▼

Delta spec sections are matched to main spec requirements by name: ADDED requirements are appended, MODIFIED ones replaced, REMOVED ones deleted after recording Reason and Migration notes, and RENAMED ones renamed while preserving scenarios.

Can I archive a change with incomplete tasks?▼

Only in exceptional cases: the orchestrator must explicitly instruct stale-checkbox reconciliation, and apply-progress plus verify-report must prove every unchecked task is complete. The reconciliation reason is recorded in the archive report.

What artifact store modes does sdd-archive support?▼

Four modes: engram persists artifacts as observations only, openspec performs filesystem merge and folder moves, hybrid does both, and none returns a closure summary without 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
MiDouTechMiDouTech

openspec-archive-change

Archive completed openspec changes into date-prefixed directories after verification.

Official
Advanced