skills.rest
etrigan16
etrigan16COMMUNITY
Explore all skills by this author →
GitHub

sdd-archive

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

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

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 a dated archive, which is error-prone when done manually and risks stale task states or unverified work being recorded as final. ## 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 review receipts are missing, tasks remain unchecked, or CRITICAL verification issues exist. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes with a mandatory archive report as the audit trail. - Use Case: After an orchestrator finishes implementing and verifying a change, this sub-agent merges the delta specs, moves the change folder to openspec/changes/archive/YYYY-MM-DD-{change-name}/, and persists a final-state 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 YYYY-MM-DD prefix, and persists an archive report.

What blocks the SDD archive step from completing?▼

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

How does delta spec merging work in OpenSpec archiving?▼

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

Can I archive a change with incomplete tasks?▼

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

What artifact store modes does the archive phase support?▼

Four modes are supported: engram stores 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→
kurojskurojs
2

sdd-onboard

Guides users through an SDD onboarding cycle on their actual codebase to implement a small, safe improvement.

Community
Advanced
RamonsDkaRamonsDka
1

sdd-archive

Merge delta specs into main specs and archive change folders.

Community
Advanced
zaxbysaucezaxbysauce
437

qa-sweep

Coordinate parallel sub-agents with adversarial review and 95% confidence gates.

Community
Advanced
mrp4stenmrp4sten
3

sdd-archive

Merge delta specs into main specs and archive changes with ISO date paths.

Community
Advanced