Menu
Archive a completed change or effort — move its folder to context/archive/ and stamp it archived.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/dikamilo/dx-workflow --skill dx-archiveThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | dx-archive |
| description | Archive a completed change or effort — move its folder to context/archive/ and stamp it archived. |
| argument-hint | ["change-id or effort-id"] |
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.
The argument is one id. Find its home:
context/changes/<id>/ → it's a change.context/efforts/<id>/ → it's an effort.context/archive/? Say it's already archived.)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.
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.
context/archive/<today>-<id>/ where <today> is date +%F. If it already exists, fail loud and stop.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).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.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.