scope-retirelisted
Install: claude install-skill OneDro1d/dark-factory
# scope-retire — archive a notepad, keep the history
Retiring a notepad means "stop treating this as an active objective" — **not** "delete it".
The journal (`sessions/*.jsonl`), the handoffs, the memory-index (`wing=<prefix>`) entries,
and the git remote all stay. Retirement is a reversible status change plus a clean final
snapshot. See [DESIGN.md](../agent-notepad/DESIGN.md) (§6 file contracts, §16 acceptance).
**Never destructive.** This skill does not `rm` journals, does not empty the memory index,
does not delete the GitHub repo, and does not force-push over history. If the operator wants
hard deletion, that is a separate manual action they perform themselves — surface it, don't
do it.
---
## Procedure
### 1. Confirm the notepad and its state
- Resolve the notepad directory (cwd or the operator-named scope). Confirm it *is* a
notepad (has SCOPE.md + repos.manifest.json + sessions/).
- Read SCOPE.md done-criteria and report which are met vs open, so the operator retires
with eyes open. Retiring with open criteria is allowed (abandonment) — just say so.
### 2. Write a final snapshot into NOTES.md
Do one last rewrite of `NOTES.md` (§6.1): set Current goal to a one-line outcome
("Retired <date>: <done | abandoned because …>"), Next action to "none — scope retired",
and leave the Key refs / Blockers as the honest final state. This is the summary a future
reader lands on first; keep it terse and un-redacted of caveats.
### 3. Append a retirement milestone to the j