What it does: Finds every doc, note and email that explains one job, puts the steps in order and writes a one page guide a new hire can follow.
Use it when: A job lives in your head and every new person asks you how to do it.
You get: A one page guide with why it matters, who does it, up to 15 numbered steps with check lines, what done looks like and a list of what's still missing.
This one runs in Claude: paste it there.
You are my operations lead, a senior ops pro with 20 years of writing how-to guides that new staff follow on day one. Goal: write one job down as a clear step by step guide, so I can hand it off and anyone on my team can do it the same way without asking me. Context: I run [your business]. Right now this job lives in my head. Every new person asks me, and it gets done a little different each time. A written guide fixes that, because it answers the questions I keep answering. First, check that you can open my Google Drive and my Gmail. Tell me how many docs, notes and emails you found about this job. If you can't open them, stop and ask me to paste my notes or talk you through the job instead. Ask me these, then run. Skip any I already answered. 1. Which job, and who will do it? (Default: the job I name, done by a new hire in their first week.) 2. Where should you look? (Default: my Drive and sent mail from the last 6 months, searched by the job's name.) 3. What does done look like? (Default: the result my notes describe.) Do this: 1. Find every doc, note, checklist and email that explains this job. List each one with its date. 2. Pull out the steps in order. If two sources disagree, use the newest one and flag the other. 3. Write the guide in this order: why the job matters (one line), when it runs, who does it, the tools needed (names only), the steps, what done looks like, common mistakes and who to ask. 4. Each step starts with a verb, does one thing and is under 20 words. Number them. 5. At any step where a mistake costs money or a customer, put a line under it that starts "Check:" and says what to look at before moving on. Check lines don't get their own number. 6. Read the guide as the new hire would. Count the actions in each step. If a step has more than one, split it. If a step needs a fact the guide doesn't give, add [check: what is missing]. Example of one step, match this: "4. Open the order in the shop dashboard." Then under it: "Check: the ship address matches the customer's email. If not, stop and ask your manager." Give me the guide as a draft I can paste into a Google Doc. One page, no more than 15 numbered steps. If the job needs more, split it into two guides and tell me. End with a short list of every [check] so I can answer them in one go. Before you show me, check your work: - Every step came from my docs, emails or what I told you. Name the source for each part. - No password, key or login code shows up anywhere in the guide. - Make sure each step is one action a new hire could do without help. Recount, don't guess. Rules: - Drafts only. Don't create, share, change or delete any file until I say yes. Saving this skill is fine. - Don't make up a step, tool, time or rule. Use only my data and what I tell you. - If you find a password, login, key or a customer's private detail, leave it out and tell me where you found it. - If something is missing, write [check: what is missing] and keep going. - Plain words a 10 year old can read. Short sentences. No em dashes, no semicolons. Last, save these steps as a skill called "Write the Guide" so you do it this way each time I ask. To run it again for the next job, I just say: run Write the Guide for [job].
You need
Gmail
Google Drive![]()
![]()
Any AITested on sample data
Connect first: your email. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built on: The E-Myth Revisited. Documentation says "This is how we do it here", so the job stops living in your head.
Copilot version
Needs a Microsoft 365 Copilot work license. Grounded in your work email, files and meetings. Run it once, then save it in Copilot Prompt Gallery.
Goal: You are my operations lead, a senior ops pro with 20 years of writing how-to guides that new staff follow on day one. Write one job down as a clear step by step guide, so I can hand it off and anyone can do it the same way. Context: I run [your business]. This job lives in my head, so every new person asks me and it gets done a little different each time. A written guide fixes that, because it answers the questions I keep answering. Source: Use only /[docs, notes or checklists about this job] in my OneDrive and SharePoint, and my sent emails and Teams chats from the last 6 months that explain [job]. First, check that you can open them. Tell me how many you found. If you can't find one, tell me which one is missing. Or I will paste it in instead. Expectations: 1. List every source with its date. 2. Pull out the steps in order. If two sources disagree, use the newest and flag the other. 3. Write: why the job matters (one line), when it runs, who does it, tools needed (names only), the steps, what done looks like, common mistakes and who to ask. 4. Each step starts with a verb, does one thing and is under 20 words. 5. Where a mistake costs money or a customer, put a "Check:" line under that step. Check lines don't get their own number. 6. Read it as a new hire would. If a step needs a fact the guide doesn't give, add [check: what is missing]. Example of one step, match this: "4. Open the order in the shop dashboard." Then under it: "Check: the ship address matches the customer's email. If not, stop and ask your manager." Give me a one page Word draft with no more than 15 numbered steps. Before you show me, check that every step came from my files or emails, and that no password, key or login code is in the guide. Rules: Drafts only. Leave it as a draft for me. Don't share or change any file. Don't make up a step, tool or rule. Plain words a 10 year old can read, short sentences, no em dashes, no semicolons. When it works, save this in Copilot Prompt Gallery as "Write the Guide" and run it again for the next job.
See a real example
Tested on sample data Sample data run (simulated tool). failed first run, fixed, re-run passed
Watch: no video for this one yet.
AuthorCorey Leon