The procedure that survives you not being in the room.
The tool that interrogates how you actually do a task, finds the steps you've stopped noticing you're doing, and turns it into a procedure someone who's never done it could actually follow.
The gap between how an expert does a task and how they describe doing it is usually large, and invisible to the expert. They skip steps that have become automatic and describe the happy path while silently handling exceptions from muscle memory.
A procedure built from a five-minute verbal explanation inherits all of these gaps. This tool interrogates the task the way an outsider would, until what's left is something a new hire could actually run.
The procedure, minus the gaps.
Same task, same five-minute description, run two ways.
An agency owner has been processing new client onboarding personally for two years and needs to hand it to an operations coordinator.
You ask Claude to write up your process from a quick description. It produces a clean, three-step summary: set up the folder, send the welcome email, book the kickoff.
It reads fine and a new hire following it exactly would still get it wrong, because "set up the folder" was actually six specific sub-steps you do automatically and never mentioned.
It unpacks the steps you skipped because they'd become automatic:
- →"Set up their folder" becomes five specific actions, including a manual name-spelling check learned the hard way
- →A decision branch for Enterprise versus Standard tier, previously undocumented
- →The one recurring exception, a CRM mismatch, and exactly what to do about it
The finished SOP includes a completion checklist specific enough that someone could verify the task was done right without asking you, which was the actual point of writing it down.
The cold version summarized what you do. This documented what you actually do.
- ✦Operators delegating a task they've been doing themselves
- ✦Managers onboarding a new hire onto a recurring process
- ✦Anyone documenting a process before going on leave
- →sop-writer.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to
~/.claude/skills/ - →sop-writer-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
- →A README inside the zip with install steps for Claude, ChatGPT, Gemini, and the API
What it does with a real question.
I do our monthly client invoicing by hand and nobody else knows how. It involves pulling hours from the time tracker, checking them against the retainer agreement, adjusting for rollover, raising the invoice in the accounting tool and emailing it with a summary. I want to hand it to a part-time bookkeeper.
Your five-step summary is a map of where the hidden steps are. "Checking hours against the retainer" and "adjusting for rollover" sound like single actions, but they're almost certainly where you make judgment calls you no longer notice: Do you round time entries? Do you ignore entries logged to the wrong project? Does rollover expire, cap, or apply to overages? What do you do when hours land at 103% of retainer? A bookkeeper can't learn those by watching you once, and they're the steps most likely to produce a wrong invoice that a client notices.
My position: this is delegable, but not yet, and not by writing it up from memory. Right now you can't say what a correct invoice looks like except "the one I'd send." Fix that first. For each client, the SOP needs a checkable answer: hours pulled, retainer allowance, prior rollover, adjustment applied, and final billable amount, each traceable to a source.
Next move: when you run next month's invoices, do the most complicated client first, narrating aloud or recording your screen, and stop yourself every time you say "just" or "obviously." Write down
The full Tool runs the whole procedure and writes the complete deliverable, not this excerpt.
Written by claude-sonnet-5-5 with this Tool loaded, 2026-10-11. Checked automatically for length and for copied framework text.
No subscription · free updates within v1.x
Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable
Before you buy.
How is this different from just asking Claude directly?
Asked cold, Claude summarizes your quick verbal description into a clean-looking but incomplete procedure, because it can't see the steps you skipped without knowing to ask about them. This interrogates each step specifically, finds the judgment calls and exceptions you left out, and produces a procedure a genuine outsider could follow.
Will this work with ChatGPT, Gemini, and other LLMs?
Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.
Can I share this with my team?
It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Tool itself in the hands of a whole team, email hello@authority.md about team licensing.
What if it doesn't work for me?
If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.
SOP Writer is a documentation tool. It produces a first draft procedure; test it by having someone unfamiliar with the task actually follow it before treating it as final.