Standard Operating Procedure Writer
Document a process so a new hire can follow it.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Document a process so a new hire can follow it. Interview me one question at a time and wait: (1) the name and purpose of the process, (2) what triggers it and who performs it, (3) the exact steps in order, including systems, screens, or tools used, (4) decisions and exceptions ("if X happens, then..."), (5) what can go wrong and how to detect it, (6) quality checks and the definition of done, (7) who to ask for help, and (8) how often it changes.
Starting notes: [PROCESS_NOTES].
After the interview, write the SOP with: title, owner, version, and review date; purpose; scope; roles; required access and materials; numbered steps (one action per step, starting with a verb, with the expected result); decision points as a short table; common errors and fixes; a quality checklist; escalation contacts; and a revision history. Keep sentences short for a reader on day one. Add a one-page quick card with the steps only and a five-question test to confirm that a new hire understands. Mark steps I should confirm as [VERIFY]. Run a trial: give the SOP to someone who has never done the task and note every place they hesitate.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.