sdd-archive

Archives completed SDD changes by syncing delta specs into main specs and moving change folders.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill sdd-archive-carloswilliamsr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/CarlosWilliamsR/SketchOS/tree/main/.config/opencode/skills/sdd-archive
Command: npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill sdd-archive-carloswilliamsr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing out a spec-driven development change requires merging delta specs into the source-of-truth specs and moving the change folder into an archive without losing or altering any bytes, which is error-prone when done manually. ## Core Features & Use Cases - Delta Spec Sync: Merges ADDED, MODIFIED, REMOVED, and RENAMED requirements from delta specs into main specs while preserving untouched requirements. - Mechanical Archive Move: Moves the change folder to a date-prefixed archive directory using shell-only copy/move with mandatory diff -r readback verification. - Gate Enforcement: Blocks archiving when tasks remain unchecked, CRITICAL verify issues exist, or a native review receipt fails validation. - Use Case: After implementation and verification of a change complete, the orchestrator delegates to this sub-agent to produce a final archive report and close the SDD cycle with a trustworthy audit trail. ## Quick Start Delegate to the sdd-archive sub-agent to archive the completed change, sync its delta specs into the main specs, and produce the final archive report.

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 OpenSpec change?

Delegate to the sdd-archive sub-agent after implementation and verification pass. It syncs delta specs into openspec/specs, moves the change folder to openspec/changes/archive with a YYYY-MM-DD prefix, and verifies the move with a diff -r readback.

How does delta spec merging into main specs work?

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 unchecked tasks in tasks.md?

No. Unchecked implementation tasks block archiving; sdd-apply must mark them complete first. Only with explicit orchestrator instruction and proof from apply-progress and verify-report may stale checkboxes be reconciled, recorded in the archive report.

Why does archive fail when shell access is unavailable?

Archival requires mechanical shell copies (cp -R, mv, git mv) verified by diff -r, because routing file bytes through model Read/Write can silently truncate content. Without shell access the skill stops and reports blocked rather than falling back.

What blocks archiving besides incomplete tasks?

CRITICAL issues in verify-report always block with no override. A present reviewGate with any result other than allow (pending, malformed, scope-changed, invalidated, escalated) also blocks, and workspace-planning actionContext stops all archive operations.