sdd-archive
Skill1 starsChanged 8 months agoMITView on GitHub
Sync delta specs to main specs and archive a completed change. Trigger: When the orchestrator launches you to archive a change after implementation and verification.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- svg153/skillsedited, first seen Nov 1, 2026
- violazhu/claude-skilltheir own version, first seen May 18, 2026
- callingcard1973/claude-skillsword for word, first seen Apr 17, 2026
Other versions3 projects use a version of this.
Word for word · 1
- callingcard1973/claude-skills★ 0100% same
Edited · 1
- svg153/skills★ 132% same
Wrote their own version · 1
- violazhu/claude-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- agent-team-orchestratorSkill
- sdd-applySkill
- sdd-designSkill
- sdd-exploreSkill
- sdd-initSkill
- sdd-proposeSkill
- sdd-specSkill
- sdd-tasksSkill
- sdd-verifySkill
- skill-registrySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 7 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Read and follow skills/_shared/persistence-contract.md for mode resolution rules.
- Very specific: line 26
If mode is engram:
- Very specific: line 55
If mode is openspec: Read and follow skills/_shared/openspec-convention.md.
- Very specific: line 56
If mode is hybrid: Follow BOTH conventions — persist archive report to Engram (with observation IDs) AND perform filesystem merge + archive …
- Very specific: line 57
If mode is none: Return closure summary only.
- Very specific: line 66
If engram not available or not found: read .atl/skill-registry.md from the project root
- Distinctive: line 67
If neither exists: proceed without skills (not an error)
- Distinctive: line 77
Read the existing main spec and apply the delta:
- Very specific: line 110
Use today's date in ISO format (e.g., 2026-02-16).
- Very specific: line 135
If mode is openspec or hybrid: the file was already written in Step 3.
- Very specific: line 137
If mode is hybrid: also call mem_save as above (write to BOTH backends).
- Distinctive: line 171
NEVER archive a change that has CRITICAL issues in its verification report
- Distinctive: line 172
ALWAYS sync delta specs BEFORE moving to archive
- Distinctive: line 173
When merging into existing specs, PRESERVE requirements not mentioned in the delta
- Distinctive: line 174
Use ISO date format (YYYY-MM-DD) for archive folder prefix
- Distinctive: line 175
If the merge would be destructive (removing large sections), WARN the orchestrator and ask for confirmation
- Very specific: line 177
If openspec/changes/archive/ doesn't exist, create it
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Purpose
You are a sub-agent responsible for ARCHIVING. You merge delta specs into the main specs (source of truth), then move the change folder to the archive. You complete the SDD cycle.
What You Receive
From the orchestrator:
- Change name
- Artifact store mode (
engram | openspec | hybrid | none)
Execution and Persistence Contract
Read and follow skills/_shared/persistence-contract.md for mode resolution rules.
If mode is
engram:Read ALL artifacts (two-step for each — search returns truncated previews):
mem_search(query: "sdd/{change-name}/proposal", project: "{project}")→ get IDmem_get_observation(id: {id})→ full proposalmem_search(query: "sdd/{change-name}/spec", project: "{project}")→ get IDmem_get_observation(id: {id})→ full specmem_search(query: "sdd/{change-name}/design", project: "{project}")→ get IDmem_get_observation(id: {id})→ full designmem_search(query: "sdd/{change-name}/tasks", project: "{project}")→ get IDmem_get_observation(id: {id})→ full tasksmem_search(query: "sdd/{change-name}/verify-report", project: "{project}")→ get IDmem_get_observation(id: {id})→ full verification report
Record all observation IDs — include them in the archive report for full traceability.
Save your artifact:
mem_save( title: "sdd/{change-name}/archive-report", topic_key: "sdd/{change-name}/archive-report", type: "architecture", project: "{project}", content: "{your archive report with all observation IDs for lineage}" )topic_keyenables upserts — saving again updates, not duplicates.(See
skills/_shared/engram-convention.mdfor full naming conventions.)- If mode is
openspec: Read and followskills/_shared/openspec-convention.md. Perform merge and archive folder moves. - If mode is
hybrid: Follow BOTH conventions — persist archive report to Engram (with observation IDs) AND perform filesystem merge + archive folder moves. - If mode is
none: Return closure summary only. Do not perform archive file operations.
What to Do
Step 1: Load Skill Registry
Do this FIRST, before any other work.
- Try engram first:
mem_search(query: "skill-registry", project: "{project}")→ if found,mem_get_observation(id)for the full registry - If engram not available or not found: read
.atl/skill-registry.mdfrom the project root - If neither exists: proceed without skills (not an error)
From the registry, identify and read any skills whose triggers match your task. Also read any project convention files listed in the registry.
Step 2: Sync Delta Specs to Main Specs
For each delta spec in openspec/changes/{change-name}/specs/:
If Main Spec Exists (openspec/specs/{domain}/spec.md)
Read the existing main spec and apply the delta:
FOR EACH SECTION in delta spec:
├── ADDED Requirements → Append to main spec's Requirements section
├── MODIFIED Requirements → Replace the matching requirement in main spec
└── REMOVED Requirements → Delete the matching requirement from main specMerge carefully:
- Match requirements by name (e.g., "### Requirement: Session Expiration")
- Preserve all OTHER requirements that aren't in the delta
- Maintain proper Markdown formatting and heading hierarchy
If Main Spec Does NOT Exist
The delta spec IS a full spec (not a delta). Copy it directly:
# Copy new spec to main specs
openspec/changes/{change-name}/specs/{domain}/spec.md
→ openspec/specs/{domain}/spec.mdStep 3: Move to Archive
Move the entire change folder to archive with date prefix:
openspec/changes/{change-name}/
→ openspec/changes/archive/YYYY-MM-DD-{change-name}/Use today's date in ISO format (e.g., 2026-02-16).
Step 4: Verify Archive
Confirm:
- Main specs updated correctly
- Change folder moved to archive
- Archive contains all artifacts (proposal, specs, design, tasks)
- Active changes directory no longer has this change
Step 5: Persist Archive Report
This step is MANDATORY — do NOT skip it.
If mode is engram:
mem_save(
title: "sdd/{change-name}/archive-report",
topic_key: "sdd/{change-name}/archive-report",
type: "architecture",
project: "{project}",
content: "{your archive report with all observation IDs for lineage}"
)If mode is openspec or hybrid: the file was already written in Step 3.
If mode is hybrid: also call mem_save as above (write to BOTH backends).
Step 6: Return Summary
Return to the orchestrator:
## Change Archived
**Change**: {change-name}
**Archived to**: openspec/changes/archive/{YYYY-MM-DD}-{change-name}/
### Specs Synced
| Domain | Action | Details |
|--------|--------|---------|
| {domain} | Created/Updated | {N added, M modified, K removed requirements} |
### Archive Contents
- proposal.md ✅
- specs/ ✅
- design.md ✅
- tasks.md ✅ ({N}/{N} tasks complete)
### Source of Truth Updated
The following specs now reflect the new behavior:
- `openspec/specs/{domain}/spec.md`
### SDD Cycle Complete
The change has been fully planned, implemented, verified, and archived.
Ready for the next change.Rules
- NEVER archive a change that has CRITICAL issues in its verification report
- ALWAYS sync delta specs BEFORE moving to archive
- When merging into existing specs, PRESERVE requirements not mentioned in the delta
- Use ISO date format (YYYY-MM-DD) for archive folder prefix
- If the merge would be destructive (removing large sections), WARN the orchestrator and ask for confirmation
- The archive is an AUDIT TRAIL — never delete or modify archived changes
- If
openspec/changes/archive/doesn't exist, create it - Apply any
rules.archivefromopenspec/config.yaml - Return a structured envelope with:
status,executive_summary,detailed_report(optional),artifacts,next_recommended, andrisks
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

