skills.rest
zMynxx
zMynxxCOMMUNITY
Explore all skills by this author →
GitHub

sdd-archive

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

Updated Jun 5, 2026
Search Tags:#archive#sdd#audit trail#change management#spec-driven development#openspec#delta specs
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-archive-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/sdd-archive
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-archive-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed spec-driven development changes leave stale delta specs and scattered change folders, making it hard to keep the main specification as a trustworthy source of truth and to preserve a clean audit trail. ## Core Features & Use Cases - Delta Spec Merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED requirements from delta specs into the main specs while preserving untouched requirements. - Task Completion Gate: Blocks archiving when unchecked implementation tasks or CRITICAL verification issues remain, enforcing SDD discipline. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, moving change folders to a date-prefixed archive and persisting an 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 Delegate to the sdd-archive sub-agent to archive the completed change and sync its delta specs into the main specifications.

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

Delegate to the sdd-archive sub-agent after implementation and verification pass. It merges delta specs into the main specs, moves the change folder to openspec/changes/archive/YYYY-MM-DD-{change-name}/, and persists an archive report.

How does delta spec merging work in spec-driven development?▼

Delta specs declare ADDED, MODIFIED, REMOVED, and RENAMED requirements. The archive step matches requirements by name in the main spec, applies each operation, and preserves all requirements not mentioned in the delta.

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

No. Unchecked implementation tasks block archiving and return a blocked status. Only an explicit orchestrator override with apply-progress and verify-report proof allows exceptional stale-checkbox reconciliation, recorded in the archive report.

What happens if the verify report contains CRITICAL issues?▼

Archiving is always blocked when the verification report contains CRITICAL issues. No user override is accepted for CRITICAL issues, so the change must be fixed and re-verified before the SDD cycle can close.

Does sdd-archive support artifact stores other than OpenSpec files?▼

Yes. It supports engram mode (artifacts stored as observations with recorded IDs), hybrid mode (both Engram and filesystem operations), and none mode (closure summary only with no file operations).

Related Skills

Explore More Software Engineering Skills→
albersgalbersg

sdd-verify

Verifies SDD change implementations by executing tests and validating spec compliance.

Community
Advanced
statick88statick88
1

sdd-archive

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

Community
Advanced
rhussrhuss
107

using-superpowers-sdd

Route SDD conversations to brainstorm, spec, implementation, evolve, or verification workflows.

Community
Basic
accidental-hedge-fundaccidental-hedge-fund
3

openspec-archive-change

Archive completed openspec experimental changes to dated directories with validation.

Official
Intermediate