Merge delta specs into main specifications and archive change folders.
npx skills add https://github.com/sebasmzg/sebas.dot --skill sdd-archive-sebasmzg
Please help me install this Agent Skill. Skill: sdd-archive Source: https://github.com/sebasmzg/sebas.dot/tree/main/.config/opencode/skills/sdd-archive Command: npx skills add https://github.com/sebasmzg/sebas.dot --skill sdd-archive-sebasmzg
This Skill automates the finalization and archival of software design documentation changes by merging delta specifications into the canonical specs and creating an auditable archive after verification, removing manual merging and traceability overhead.
Archive the change named feature-x by merging its delta specs into main specs, recording all observation IDs, and moving the change folder to openspec/changes/archive/YYYY-MM-DD-feature-x according to the project mode.
High-intent search queries and answers about installing and using this skill.
To merge delta specs into main specifications, apply openspec filesystem operations that add, modify, or remove requirements while preserving existing markdown structure, then move the change folder into a dated archive directory.
Archiving software design documentation changes requires merging delta specifications into canonical specs and creating an auditable archive after verification, supporting engram-only, openspec-only, hybrid, or none modes for finalization.
Engram supports spec archival traceability by using mem_search to locate artifacts, mem_get_observation to retrieve full content, and mem_save to persist an archive report that records mandatory observation IDs for full verification traceability.
Yes, the none mode provides a dry-run summary without applying destructive merges. The archival workflow includes safeguards against destructive changes, ensuring openspec filesystem merges only proceed after verification gating is explicitly satisfied.
Automated spec merging should not proceed when verification gating is incomplete or unrelated markdown content cannot be safely preserved. The archival workflow enforces mandatory observation ID recording to prevent untraceable destructive spec modifications.
You need openspec filesystem support for delta merges and archive moves, plus Engram mem_search, mem_get_observation, and mem_save flows to record observation IDs. The workflow operates in engram-only, openspec-only, hybrid, or none modes depending on available infrastructure.
sebasmzgCreate technical design documents from proposals and specs.
bacocoArchive completed OpenSpec changes by merging delta specs into living specifications.
adacosdevMerge delta specs into main specifications and archive completed change folders.
arestivoMerge delta specs into main OpenSpec specifications deterministically.
