claude-sops

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.

Show what is in the SOP library — everything, or filtered by tag, or only the procedures that have gone stale. Use when the user asks what SOPs they have, whether one exists for something, which ones need reviewing, or wants an overview of their procedures before deciding what to write next.

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.

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.

Commit and push the SOP library, or pull it down, so the same procedures are available on every machine. Use when the user asks to sync, save, push or back up their SOPs, when setting up a second machine, and at the end of any session that added or changed a procedure.

Capture a recurring procedure as a new SOP in the user's library — usually written from what just happened in this session, while the details are still known. Use when the user says "write this up as an SOP", "remember how we did this", "add this to my procedures", or when the same multi-step sequence has now come up twice and nothing in the index covers it.