Merge delta specifications into main specs and archive completed SDD changes.
npx skills add https://github.com/kurojs/EnderDots --skill sdd-archive-kurojs
Please help me install this Agent Skill. Skill: sdd-archive Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/sdd-archive Command: npx skills add https://github.com/kurojs/EnderDots --skill sdd-archive-kurojs
This Skill resolves the risk of losing change history by merging finalized delta specifications into the main “source of truth” and then archiving the full completed change for traceability.
Run the sdd-archive skill as the executor after implementation and verification, providing the change name and artifact store mode so it can sync specs, archive the change, and persist the archive-report.
High-intent search queries and answers about installing and using this skill.
To merge delta specifications into main specs for an audit trail, you merge added, modified, and removed requirements from delta files into existing main specs while preserving unspecified requirements. This ensures your finalized changes are synchronized into the source of truth.
The best way to archive completed SDD changes with ISO date prefixes is to relocate the entire finalized change folder into an archive location using a YYYY-MM-DD prefix. This creates an immutable audit trail that ensures long-term traceability of your modifications.
Yes, sdd-archive works with openspec, engram, hybrid, and none artifact modes. It applies to executor-phase workflows in these modes by driving requirement updates from delta spec files and mandating archive-report persistence keyed by the change name.
No, you cannot archive a change folder if critical verification issues exist. The process includes verification guardrails that encourage checking main spec updates, archive contents, and active directory cleanup, with strict rules to avoid archiving when critical issues are detected.
To persist an archive-report keyed by change name after spec synchronization, you save it using the architecture topic keyed by sdd/{change-name}/archive-report. This mode-aware persistence step guarantees the archived change remains traceable within your workflow.
bacocoGenerate OpenSpec change proposals with tasks and delta specifications.
yakksiekMove completed change folders to an archive directory and update related documents.
bacocoArchive completed OpenSpec changes by merging delta specs into living specifications.
SAPMerge delta specifications into main OpenSpec specs under openspec/specs.
