Sdd Archive
Finalize a completed Specification-Driven Development (SDD) change by archiving a closure report to engram and refreshing project memory in ai-context.
Overview
sdd-archive is an agent skill most often used in Operate (also Build, Ship) that closes a completed SDD change by verifying engram artifacts, confirming with you, and saving an irreversible archive report plus optional a
Install
npx skills add https://github.com/fearovex/claude-config --skill sdd-archiveWhat is this skill?
- Blocks archive when CRITICAL SDD artifacts (proposal, tasks) are missing in engram
- WARNs on missing design/specs with a two-option proceed prompt
- Requires explicit user confirmation before irreversible closure
- Resolves skill path: project `.claude/skills/sdd-archive` overrides global catalog
- Writes archive report to engram and optionally updates ai-context memory
- 2 CRITICAL artifact types (proposal, tasks)
- 2 WARNING artifact types (design, specs)
Adoption & trust: 1 installs on skills.sh; 1 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You finished SDD work but have no enforced, searchable closure record and your project memory still reflects the open change.
Who is it for?
Teams or solo builders running SDD with engram who need a gated, documented end to a named change.
Skip if: Skipping when proposal or tasks were never stored in engram, or when you only want a casual chat recap without SDD artifacts.
When should I use this skill?
/sdd-archive <change-name>, archive change, finalize SDD cycle, close change, sdd archive
What do I get? / Deliverables
After confirmation, you get a persisted archive report in engram and updated ai-context so the SDD cycle is formally closed and the next change can start clean.
- Archive report in engram
- Optional ai-context memory update
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Archiving is end-of-cycle housekeeping after delivery work—Prism shelves it under Operate as the canonical “close the loop” step, not because earlier phases never produced the artifacts. Iterate covers post-ship cycle completion: validating artifacts, persisting history, and updating memory so the next change starts from truth.
Where it fits
After tasks and design land in engram, you name the change and prepare for verify before archive.
Release checklist is done; you archive the SDD change so launch memory matches what shipped.
Post-incident fix cycle completes; you archive so iterate work does not leave orphan open changes.
How it compares
Use as the formal SDD cycle closer—not as a generic git commit message or unstructured session summary.
Common Questions / FAQ
Who is sdd-archive for?
Solo builders and small teams using SDD orchestration with engram and optional ai-context who need a verified, irreversible archive step after verify completes.
When should I use sdd-archive?
At Operate/iterate when a change is done; also at the tail of Build/pm or Ship/launch when you are finalizing an SDD change name after specs, tasks, and verify artifacts exist in engram.
Is sdd-archive safe to install?
It performs irreversible closure actions after explicit confirmation; review the Security Audits panel on this Prism page and inspect project-local overrides under `.claude/skills/sdd-archive` before trusting it in production repos.
SKILL.md
READMESKILL.md - Sdd Archive
# sdd-archive > Closes a completed SDD change and persists an archive report. **Triggers**: `/sdd-archive <change-name>`, archive change, finalize sdd cycle, close change, sdd archive --- ## Purpose Archiving is the **final step** of the SDD cycle. It validates completeness, saves a closure record, and updates the project memory layer. It is irreversible — I confirm with the user before executing. --- ## Process ### Skill Resolution When the orchestrator launches this sub-agent, it resolves the skill path using: ``` 1. .claude/skills/sdd-archive/SKILL.md (project-local — highest priority) 2. ~/.claude/skills/sdd-archive/SKILL.md (global catalog — fallback) ``` Project-local skills override the global catalog. See `docs/SKILL-RESOLUTION.md` for the full algorithm. --- ### Step 1 — Verify it is archivable #### Completeness Check Before reading the verify report, I check for required SDD artifacts in engram. Artifact exists if `mem_search` returns results. **CRITICAL artifacts** (block with no proceed option): proposal, tasks **WARNING artifacts** (present two-option prompt): design, specs **Check order:** 1. Check CRITICAL artifacts first. If any are absent: ``` CRITICAL — Cannot archive "[change-name]" The following artifacts are required for a valid SDD cycle but are missing: - proposal (required — CRITICAL) - tasks (required — CRITICAL) Return and complete the missing phases before archiving. No proceed option is available. ``` List only the artifacts that are actually absent. Halt immediately. Do NOT evaluate WARNING artifacts. 2. If CRITICAL passes, check WARNING artifacts. If any are absent: ``` WARNING — Incomplete cycle detected for "[change-name]" The following artifacts are missing: - design (recommended — WARNING) - specs (recommended — WARNING) Choose: 1. Return and complete the missing phases (/sdd-spec, /sdd-design) 2. Archive anyway — I acknowledge these phases were intentionally skipped Reply 1 or 2: ``` List only the artifacts that are actually absent. Wait for the user to reply: - **Option 1 selected**: halt. The user returns to complete the missing phases. - **Option 2 selected**: record the skipped phases (for use in Step 4 closure) and continue. 3. If all CRITICAL and WARNING artifacts are present: produce no output and continue immediately. **Note**: exploration is explicitly excluded from this check. Its absence MUST NOT trigger any CRITICAL or WARNING output. --- I read the verify report artifact if it exists: - `mem_search(query: "sdd/{change-name}/verify-report")` → `mem_get_observation(id)`. If there are unresolved CRITICAL issues: ``` No archiving allowed. The verification report has [N] critical issues: - [issue 1] - [issue 2] Resolve the issues and run /sdd-verify again before archiving. ``` If there is no verification report, I inform the user and ask whether to proceed anyway. **User-docs review checkbox** (non-blocking): After reading the verify-report (if it exists), surface the user-docs review item status: ``` User docs review checkbox: [CHECKED / UNCHECKED / ABSENT] ``` - CHECKED: verify-report contains `[x] Review user docs` — good - UNCHECKED: verify-report contains `[ ] Review user docs` — remind the user to check if this change affects user-facing docs - ABSENT: the checkbox is not in the verify-report — no action needed (older changes pre-date this requirement) This check is **non-blocking** — the archive operation continues regardless of the checkbox state. ### Step 2 — Confirm with the user ``` Do you confirm archiving the change "[change-name]"? This will perform the following actions: 1. Save an archive clo