菜单
Retire an SOP that no longer applies — moving it to the library's archive, or deleting it outright when asked. Use when the user says a procedure is obsolete, that they do not do it that way any more, or that a system it depends on is gone; and when a replacement SOP has been written for the same job.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/danielrosehill/Claude-SOPs --skill sop-remove命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Amend an existing SOP — fix a step that has drifted, add a failure mode that was just hit, adjust its trigger or autonomy, or re-date last_verified after a successful run. Use when the user says an SOP is out of date or wrong, when following one produced a surprise, and routinely at the end of any SOP run that worked.
Find the user's standard operating procedure for the task at hand and follow it. Reads the SOP index, matches the situation, opens exactly one procedure and executes it at the autonomy level that SOP declares. Use whenever a multi-step recurring task comes up — deploying, publishing, filing, ordering, onboarding, closing a period — before working the sequence out from scratch, and whenever the user says "run the SOP for X" or "how do I usually do X".
Set up the SOP library for the first time — create the folder, make it a private git repo, record the path in the vault, and add the pointer block to the user's CLAUDE.md. Also the skill for moving the library somewhere else, or cloning an existing SOP repo onto a second machine. Use when the user asks to start keeping SOPs, when another sop-* skill finds no library, or when they mention mirroring their procedures across machines.
基于 SOC 职业分类
正在显示 SKILL.md
| name | sop-remove |
| description | Retire an SOP that no longer applies — moving it to the library's archive, or deleting it outright when asked. Use when the user says a procedure is obsolete, that they do not do it that way any more, or that a system it depends on is gone; and when a replacement SOP has been written for the same job. |
Default to archiving. Deletion is available and is sometimes right, but a retired procedure is often the only surviving record of how a system used to work, and that is not obvious until someone needs it.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" show <id>
Then check what the retirement really is:
| Situation | What to do instead |
|---|---|
| One step is wrong | sop-edit. Do not retire a procedure over a renamed flag. |
| It has been superseded | Write the replacement first, list this id in the new one's supersedes, then retire. |
| It is stale, not obsolete | Staleness means unverified. Unverified is not the same as untrue. |
| Genuinely obsolete | Retire it. |
Ask the user which of these it is if the request is ambiguous — "we don't do that any more" covers all four.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" retire <id>
Moves it to archive/<YYYY-MM-DD>-<id>.md and reindexes. Archived files are not
in INDEX.md, so the dispatcher will not find them — which is the point — but
they remain readable and greppable.
Add one line at the top of the archived file saying why it was retired and what replaced it, if anything. In two years that line will be the only thing making the file interpretable.
Only when the user asks for deletion specifically, and only after saying what is being lost.
LIB="$(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" path)"
git -C "$LIB" rm "<id>.md"
Use git rm rather than rm — the history keeps the content, which makes this
recoverable and is worth saying to the user as reassurance.
If they want it gone from history too, that is a rewrite of a repo they mirror across machines. Say what that involves and let them decide; do not start it as part of a retirement.
LIB="$(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" path)"
ROOT="$(python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" repo)"
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" index
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sop.py" validate
git -C "$ROOT" add -- "$LIB"
git -C "$ROOT" commit -m "Retire SOP: <id>"
Stage $LIB, not -A — the repo root holds other tools' folders too.
validate after retiring catches the dangling reference — another SOP whose
supersedes or ## Notes points at the id that just left. Fix those in the
same commit; a link to a procedure that is not there reads as a bug in the
library rather than a deliberate retirement.