How do I install the Dx Archive skill?

Run npx skillmds@latest add dikamilo/dx-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 Dx Archive safe to use?

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

Which AI agents work with Dx 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 Dx Archive free to use?

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

Who published Dx Archive?

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

Dx Archive by dikamilo — Agent Skill

Name: Dx Archive
Author: dikamilo

File contents

dx-archive

Retire a finished container. One id in, one folder moved, one stamp written. No registry — the archive is just where done work lives.

Guard. If the id resolves to nothing, or the folder can't move cleanly, do nothing and say why. Never half-move.

Resolve

The argument is one id. Find its home:

context/changes/<id>/ → it's a change.
context/efforts/<id>/ → it's an effort.
Neither, or both → fail loud: print what you looked for and stop. (Already under context/archive/? Say it's already archived.)

Effort gate — children first

An effort is done only when every child change is already archived. Before moving an effort, read its roadmap.md, and for each linked child change check for archived_at (derive it — scan the child's change.md, don't trust a checkbox). If any child is still open, list them and ask before continuing. The user may override.

Review gate — unresolved findings

For a change, check reviews/impl-review.md. If it has any finding with Resolution: PENDING, warn — "N unresolved impl-review finding(s) — /dx-review-triage impl to address them first" — and ask whether to archive anyway. The user may override.

Move and stamp

Destination: context/archive/<today>-<id>/ where <today> is date +%F. If it already exists, fail loud and stop.
Stamp the moved container's change.md (or effort.md): set status: archived and archived_at: to today's date (date +%F, same format as created/updated — no other field in the schema carries a finer timestamp); bump updated:. Leave every other field alone. For the exact schema, invoke dx-references with topic change-md (a change) or effort-md (an effort).
Move the whole folder: prefer git mv so history follows; fall back to mv (warn) if git is unavailable. Confirm the source is gone and the destination exists — if not, print a diagnostic and stop.

Done when

The folder lives at context/archive/<today>-<id>/, its identity file reads status: archived with archived_at set, and nothing remains under the old path. Print:

✓ Archived <id> → context/archive/<today>-<id>/

If it was an effort, add one line noting how many child changes it closed. Then suggest a next step (/dx-new <idea> to start fresh) and stop. Do not chain.

---name: dx-archivedescription: Archive a completed change or effort — move its folder to context/archive/ and stamp it archived.---# dx-archiveRetire a finished container. One id in, one folder moved, one stamp written. No registry — the archive is just where done work lives.**Guard.** If the id resolves to nothing, or the folder can't move cleanly, do nothing and say why. Never half-move.## ResolveThe argument is one id. Find its home:- `context/changes/<id>/` → it's a **change**.- `context/efforts/<id>/` → it's an **effort**.- Neither, or both → **fail loud**: print what you looked for and stop. (Already under `context/archive/`? Say it's already archived.)## Effort gate — children firstAn effort is done only when **every child change is already archived**. Before moving an effort, read its `roadmap.md`, and for each linked child change check for `archived_at` (derive it — scan the child's `change.md`, don't trust a checkbox). If any child is still open, **list them and ask** before continuing. The user may override.## Review gate — unresolved findingsFor a **change**, check `reviews/impl-review.md`. If it has any finding with `Resolution: PENDING`, warn — "N unresolved impl-review finding(s) — /dx-review-triage <change-id> impl to address them first" — and ask whether to archive anyway. The user may override.## Move and stamp1. Destination: `context/archive/<today>-<id>/` where `<today>` is `date +%F`. If it already exists, fail loud and stop.2. Stamp the moved container's `change.md` (or `effort.md`): set `status: archived` and `archived_at:` to today's date (`date +%F`, same format as `created`/`updated` — no other field in the schema carries a finer timestamp); bump `updated:`. Leave every other field alone. For the exact schema, invoke `dx-references` with topic `change-md` (a change) or `effort-md` (an effort).3. Move the whole folder: prefer `git mv` so history follows; fall back to `mv` (warn) if git is unavailable. Confirm the source is gone and the destination exists — if not, print a diagnostic and stop.## Done whenThe folder lives at `context/archive/<today>-<id>/`, its identity file reads `status: archived` with `archived_at` set, and nothing remains under the old path. Print:```✓ Archived <id> → context/archive/<today>-<id>/```If it was an effort, add one line noting how many child changes it closed. Then suggest a next step (`/dx-new <idea>` to start fresh) and stop. Do not chain.

Frequently asked questions

Dx Archive