skills.rest
Alountk
AlountkCOMMUNITY
Explore all skills by this author →
GitHub

sdd-archive

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

Updated Aug 5, 2026
Search Tags:#workflow#archive#sdd#audit trail#openspec#spec sync#delta specs
One-click install
npx skills add https://github.com/Alountk/Bloodbowl_Project --skill sdd-archive-alountk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/Alountk/Bloodbowl_Project/tree/main/.opencode/skills/sdd-archive
Command: npx skills add https://github.com/Alountk/Bloodbowl_Project --skill sdd-archive-alountk

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 lost traceability. ## 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: Enforces a Native Review Receipt Gate and Task Completion Gate so changes with unchecked tasks or CRITICAL verification issues cannot be archived. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, producing a mandatory archive report with observation IDs for traceability. - Use Case: After a feature change has been implemented and verified, the orchestrator delegates to this sub-agent to sync specs, move the change folder to openspec/changes/archive/YYYY-MM-DD-{change-name}/, and persist the final archive report. ## Quick Start Delegate to the sdd-archive sub-agent with the change name and artifact store mode to sync delta specs and archive the completed change.

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?▼

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

What blocks an SDD change from being archived?▼

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

Can sdd-archive handle unchecked tasks in tasks.md?▼

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

Does sdd-archive work without openspec files?▼

Yes. In engram mode all artifacts live in Engram and only the archive report is persisted with observation IDs. In none mode it returns a closure summary with no filesystem operations.

How are delta specs merged into main specs?▼

Requirements are matched 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. Untouched requirements are preserved.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

gsd:verify-work

Run the gsd-verifier agent on phase plans and task details.

Community
Intermediate
NSObjectsNSObjects
4

archiving

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

Community
Advanced
etrigan16etrigan16

sdd-archive

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

Community
Advanced
mahoushoujyo-eeemahoushoujyo-eee
15

openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts, tasks, and specification synchronization.

Community
Advanced