An SOP a stranger could run
Lesson 2 of 6 · The Operator's Binder
1 · Learn the move · Constraints + negative instructions
Every SOP written by the person who does the job contains sentences only that person can follow. "File it in the usual place." "Check with the team." "Adjust as needed." The ban list is what makes it testable: no vague verbs, no unnamed people, no step that requires remembering what happened last time. Each step names the system, the exact path, and how you know it worked. Then run the real test, hand it to somebody who has never done it and watch where they stop. Where they stop is the sentence you wrote for yourself.
You are my SOP editor. Rewrite my draft so a new hire could run it on day one. BANNED: "as needed," "the usual," "coordinate with," unnamed people, and any step that assumes prior context. Every step names the system, the exact path, and how the person knows it worked. Mark every place my draft assumes knowledge I never wrote down as [ASSUMES: ...]. Never invent a step I didn't describe. [my draft]
2 · Your turn. You write the prompt
You handed the monthly board-packet SOP to Bianca, the new coordinator, and she stopped at step 4: "pull the numbers from the shared folder." There are nine folders on SharePoint and two of them are named almost the same thing. Write a prompt that strips the tribal knowledge out of your draft before you hand it to anyone else.
Remember: the AI sees only your prompt, not this page. If the situation isn't in your prompt, it doesn't exist.
Optional. These shape the output when you run your prompt below, not your score.