A course launch had 12 moving parts.
Klaviyo flows. Stripe webhooks. Course-platform embeds. Scheduled jobs. Welcome sequences. Abandoned cart. Refunds. Pre-launch nurture. The calculator that fed the lead magnet. Post-purchase delivery. Affiliate payouts. The exit survey.
Every one was a different tool. None of them were documented.
The old way is gravity
The old way is a Notion doc.
You sit down. Write thirty pages. Ship it. Then a process changes on Tuesday and the doc is wrong by Wednesday. Nobody updates it. Nobody reads it. Six months later it shows up as "shared with you" in someone else's Notion sidebar and they wonder if it is still true.
It is not.
That is the gravity well of business documentation. It pulls energy in and outputs nothing.
The reason most teams have no working SOPs is not laziness. It is that the artifact rots faster than they can write it.
What I actually needed
I needed something that did three things.
It had to ask me the questions, instead of me staring at a blank doc.
It had to enforce a format I did not have to argue with.
It had to write the SOP in the time it took me to read it.
So I built a Claude Code skill.
What the skill does
You run /sop in any project. The skill asks you five questions about the process you are documenting.
What event triggers this process. Who owns it end to end. What the steps are, in order. What inputs and outputs flow through it. What goes wrong, and how someone recovers when it does.
Then it writes the SOP. Same six-section format every time.
Trigger. What kicks this off. The Stripe webhook. The form submission. The Monday meeting.
Owner. One name. Not a team. Not a role. A name.
Steps. Numbered. Specific. The smallest unit of work a new teammate can complete.
Inputs and outputs. What goes in. What comes out. Where the output goes next.
Failure modes. What you have seen go wrong, and the recovery path for each.
Success metric. The one number that says this process worked.
That is the only useful SOP. Anything more is decoration. Anything less is a wish.
The numbers from this launch
When I needed to onboard someone to one of the email flows last week, I sent them the SOP. They were running it inside an hour. No back-and-forth. No "did I do this right" Slack messages. The doc answered the questions before they were asked.
That is the only test of an SOP.
What the skill is not
It is not a project-management tool. It does not track work in flight.
It is not a wiki. There is no taxonomy, no permissions, no tagging.
It is not opinionated about your stack. It does not assume you use Notion or Asana or anything else. The output is plain markdown. Paste it wherever you keep things.
It is one job done well. Take a process in your head. Get it out of your head and into a one-page document that a stranger can run on Monday.
Get the skill
Install instructions are in the FAQ. If you run into a wall, hit reply on the Friday email and tell me what broke. I will fix it and update the skill.
Build one SOP. Then build another. By the end of the week your business has more documentation than it had in the prior year.
That is the whole pitch.