How do I install the Sdd Archive skill?

Run npx skillmds@latest add ahgraber/sdd-archive in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sdd Archive safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sdd Archive?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sdd Archive free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sdd Archive?

ahgraber (@ahgraber) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sdd Archive by ahgraber — Agent Skill

Name: Sdd Archive
Rating: 4.666666666666667 (3 reviews)
Author: ahgraber

File contents

SDD Archive

Complete a change by moving its directory to the archive.

SPECS_ROOT is resolved by the sdd router before this skill runs. Replace .specs/ with your project's actual specs root in all paths below.

Writing Style

Write the archive report in the voice of a professional technical writer. Prefer ASD-STE100 Simplified Technical English: short sentences, one instruction per sentence, active voice, and one term per concept. Keep identifiers, commands, paths, and RFC 2119 keywords exact.

When to Use

All tasks in tasks.md are complete (- [x])
Delta specs have been synced into main specs with sdd-sync
Ready to close out the change

When Not to Use

Tasks are incomplete — finish implementation first
Delta specs exist but haven't been synced — consider running sdd-sync first (no automatic check; user judgement)

Invocation Notice

Tell the user when this skill is running: sdd-archive. Skip the notice when the user asked for the skill by name or slash command; spelling and spacing need not match. A phrase from this skill's own trigger list is not a name — naming the work is not naming the skill.

Soft Gate

Check tasks.md for unchecked tasks before archiving.

If incomplete tasks remain:

"{N} tasks are still incomplete. Archive anyway?"

Wait for user confirmation before proceeding.

Process

Phase 1: Confirm

Confirm which change to archive (ask if multiple active changes exist)
Read tasks.md — count complete vs. total tasks
If incomplete tasks: issue soft gate warning, wait for user

Phase 2: Check Target

Target path: .specs/changes/archive/YYYY-MM-DD-<change-name>/

Where YYYY-MM-DD is today's date.

If the target already exists:

"Archive target already exists: .specs/changes/archive/{date}-{name}/. Suggest using {name}-2 or waiting until tomorrow."

Stop and ask the user how to proceed.

Phase 3: Move

mkdir -p .specs/changes/archive/
mv .specs/changes/<name>/ .specs/changes/archive/YYYY-MM-DD-<name>/

Confirm the move succeeded by checking the archive path exists.

The change's .verify/ scratch (if present) is self-gitignored, so it never enters the archived commit even though mv carries it along — leave it or delete it; it is not part of the archived record.

Phase 4: Report

Archived: .specs/changes/<name>/ → .specs/changes/archive/YYYY-MM-DD-<name>/
Tasks: {N}/{N} complete

Common Mistakes

Deleting instead of moving (archive, not delete — change history is preserved)
Archiving before syncing delta specs into main specs
Not checking for the target path existence before moving

---name: sdd-archivedescription: Use when completing and archiving a change after all tasks are done and specs are synced. Triggers: "archive the change", "complete this change", "close out the change", "finish the change", "archive".---# SDD ArchiveComplete a change by moving its directory to the archive.> `SPECS_ROOT` is resolved by the `sdd` router before this skill runs.> Replace `.specs/` with your project's actual specs root in all paths below.## Writing StyleWrite the archive report in the voice of a professional technical writer.Prefer ASD-STE100 Simplified Technical English: short sentences, one instruction per sentence, active voice, and one term per concept.Keep identifiers, commands, paths, and RFC 2119 keywords exact.## When to Use- All tasks in `tasks.md` are complete (`- [x]`)- Delta specs have been synced into main specs with `sdd-sync`- Ready to close out the change## When Not to Use- Tasks are incomplete — finish implementation first- Delta specs exist but haven't been synced — consider running `sdd-sync` first (no automatic check; user judgement)## Invocation Notice- Tell the user when this skill is running: `sdd-archive`. Skip the notice when the user asked for the skill by name or slash command; spelling and spacing need not match. A phrase from this skill's own trigger list is not a name — naming the work is not naming the skill.## Soft GateCheck `tasks.md` for unchecked tasks before archiving.If incomplete tasks remain:> "{N} tasks are still incomplete. Archive anyway?"Wait for user confirmation before proceeding.## Process### Phase 1: Confirm1. Confirm which change to archive (ask if multiple active changes exist)2. Read `tasks.md` — count complete vs. total tasks3. If incomplete tasks: issue soft gate warning, wait for user### Phase 2: Check TargetTarget path: `.specs/changes/archive/YYYY-MM-DD-<change-name>/`Where `YYYY-MM-DD` is today's date.If the target already exists:> "Archive target already exists: `.specs/changes/archive/{date}-{name}/`. Suggest using `{name}-2` or waiting until tomorrow."Stop and ask the user how to proceed.### Phase 3: Move```bashmkdir -p .specs/changes/archive/mv .specs/changes/<name>/ .specs/changes/archive/YYYY-MM-DD-<name>/```Confirm the move succeeded by checking the archive path exists.The change's `.verify/` scratch (if present) is self-gitignored, so it never enters the archived commit even though `mv` carries it along — leave it or delete it; it is not part of the archived record.### Phase 4: Report```textArchived: .specs/changes/<name>/ → .specs/changes/archive/YYYY-MM-DD-<name>/Tasks: {N}/{N} complete```## Common Mistakes- Deleting instead of moving (archive, not delete — change history is preserved)- Archiving before syncing delta specs into main specs- Not checking for the target path existence before moving

Frequently asked questions

Sdd Archive