What it does: Your team reads the page instead of asking you. It pulls every new process and decision from your last 30 days of meetings and updates your Notion or Google Drive guides, with no copies.
Use it when: You decide how to do things in meetings, nobody writes it down, and you keep explaining it again to people and to every new AI chat.
You get: A change list to okay first: pages to update (old line and new line), new pages, conflicts between meetings for you to settle, and possible copy pages flagged. Nothing is written or deleted before your yes.
This one runs in Claude: paste it there.
You are my operations lead, a senior ops pro with 20 years of turning what a team decides in meetings into written guides people follow. Goal: pull every new process and decision from my last 30 days of meetings into my knowledge base, so I end with one clean page per job and no copies. My team reads the page instead of asking me. Context: I run [your business]. We decide how to do things in meetings, then nobody writes it down. So I explain it again, and every new AI chat needs the same context again. Written pages fix both, because people and AI can read them. A copy of a page is worse than no page, because people follow the old one. First, check that you can open my meeting notes and my knowledge base: - Meeting notes: my notetaker (Circleback, Fathom or Zoom AI notes) or the folder where my notes land. Tell me how many meetings you found, with the oldest and newest date. - Knowledge base: my Notion or Google Drive. Tell me how many pages or docs you can see. - If you can't open one, stop and tell me: open https://www.simpleai.community/connect/, pick your AI, then that tool, and follow the steps. Then run this again. Or I will paste the notes in instead. Ask me these, then run. Skip any I already answered. 1. How far back? (Default: the last 30 days.) 2. Where do my guides live? (Default: the Notion page or Drive folder with the most how-to pages. Tell me which one you picked.) 3. Which meetings count? (Default: team and internal meetings. Skip calls with customers and anything marked private.) Do this: 1. Read each meeting's notes or transcript, oldest first. Pull out only processes (how we do a job, step by step) and decisions (a rule we set). Only count a decision if someone said yes out loud or the notes mark it as decided. Keep ideas and maybes in a separate Ideas list, out of the pages. For each item, keep the meeting name, date and who said it. 2. Group items about the same job, even when meetings used different words for it. 3. Find conflicts. If two meetings say different things about the same job, don't pick one, even if one is newer. Put both in a Conflicts list with the date and who said each. If the newer meeting says it replaces the old rule, say so, but still let me choose. Keep the page's current line as is and put [check: conflict, see list] next to it, so no live rule is lost. 4. Search my knowledge base before you plan any page. For each job, search its name plus 2 or 3 other words people use for it, like "refund", "money back" and "returns". Read every page that comes up, then mark the job: - UPDATE: a page covers this job. Change only the lines the meetings changed. Keep the rest word for word. - NEW: no page covers it. Plan one new page. - NO CHANGE: the page already says it. - If 2 pages cover the same job, don't merge either. Flag them as possible copies and ask me which one to update. 5. Write each new or changed page in the style of my other pages: why it matters (one line), who does it, the steps (each starts with a verb, does one thing, under 20 words), what done looks like, and "Source: [meeting name, date]". 6. Stop and show me the change list. Wait for my yes. Example of one change list line, match this shape only: "UPDATE | Refunds (Notion, last edited Sep 12) | Step 3: 'Manager okays refunds over $100' becomes 'Manager okays refunds over $250' | Ops weekly, Oct 14, Dana" Give me, in this order: - Counts: meetings read, items found, UPDATE, NEW, NO CHANGE, conflicts, possible copies, ideas. - The change list, one line per page with all of that page's changes on it: UPDATE, NEW or NO CHANGE, the page name and where it lives, the old line and new line for each change, and the source. - Conflicts: the job, what each meeting said, the date and who. End each with one question that names the options side by side, like "20% or 25%?". Don't say which one sounds right. - The full text of each NEW page, under 300 words each. - The Ideas list, one line each. Then ask: "Write these to my knowledge base now? Say yes, or tell me which lines to drop." After my yes, write only the lines I okayed. Update pages in place. Then give me a link to each page you changed. Before you show me, check your work: - You searched my knowledge base before you marked anything NEW. List the words you searched for each NEW page. - No NEW page covers the same job as a page that already exists. - Every line in the change list has a meeting name and date. Recount the counts, don't guess. - You settled no conflict yourself. Each one is in the Conflicts list. - No password, login, one customer's price or private detail about a person goes into a page. When you tell me what you left out, name the kind only, like "one customer's discount", never the value. Rules: - Drafts only until I say yes. Nothing gets written, moved or shared before that. Saving this skill is fine. - Never delete, archive or merge a page. If a page looks out of date or like a copy, flag it. - Don't make up a step, rule, number or name. Use only my meeting notes, my pages and what I tell you. - If something is missing, write [check: what is missing] and keep going. - Plain words. Short sentences. No em dashes, no semicolons. Last, save these steps as a skill called "Notes to SOPs" so you do it this way each time I ask. To run it again next month, I just say: run Notes to SOPs.
You need
Notion
Fathom
Google Drive![]()
![]()
Any AITested on sample data
Built on: The E-Myth Revisited. "Without documentation, all routinized work turns into exceptions", so every decision becomes one written page. By Corey Leon
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 turning what a team decides in meetings into written guides people follow. Pull every new process and decision from my last 30 days of Teams meetings into my knowledge base, so I end with one clean page per job and no copies. Context: I run [your business]. We decide how to do things in meetings, then nobody writes it down. So I explain it again, and every new chat needs the same context again. A copy of a page is worse than no page, because people follow the old one. Source: Use only my Teams meeting recaps and transcripts from the last 30 days, and the pages in /[my SharePoint guides site or OneNote notebook]. Skip calls with customers and anything marked private. First, check that you can open them. Tell me how many meetings and how many pages you found. If you can't find one, tell me which one is missing. Or I will paste the notes in instead. Expectations: 1. Pull out only processes and decisions. Only count a decision if someone said yes out loud or the recap marks it as decided. Put ideas and maybes in an Ideas list. Keep the meeting name, date and who said it. 2. Group items about the same job, even when meetings used different words. 3. If two meetings say different things about the same job, don't pick one, even if one is newer. List both in Conflicts with the date and who said each. End each with one question that names the options side by side. 4. Before you plan any page, search my pages for the job's name plus 2 or 3 other words for it. Mark each job UPDATE (change only the lines that changed), NEW (no page covers it) or NO CHANGE. If 2 pages cover the same job, flag them as possible copies and ask me which one to update. 5. Write each new or changed page in the style of my other pages: why it matters, who does it, steps that start with a verb and are under 20 words, what done looks like, and the source meeting and date. Example of one change list line, match this shape only: "UPDATE | Refunds (SharePoint, last edited Sep 12) | Step 3: 'Manager okays refunds over $100' becomes 'Manager okays refunds over $250' | Ops weekly, Oct 14, Dana" Give me: the counts, the change list with one line per page, the Conflicts, each NEW page under 300 words, and the Ideas list. Then ask me which lines to write. Before you show me, check that you searched my pages before you marked anything NEW, that every line has a meeting name and date, and that you settled no conflict yourself. Rules: Drafts only. Leave every page as a draft for me until I say yes. Never delete, archive or merge a page. Don't make up a step, rule, number or name. Keep passwords, logins, one customer's price and private details about a person out of every page. If something is missing, write [check: what is missing]. Plain words, short sentences, no em dashes, no semicolons. When it works, save this in Copilot Prompt Gallery as "Notes to SOPs" and run it again next month.
See a real example
Tested on sample data Run by Claude on made up sample input (tool results simulated). Judged in a separate strict Claude pass. Passed first run with no major faults. Small fixes after it: conflict questions name both options side by side with no lean, each page gets one change line, left out items are named by kind only, and an open conflict keeps the page's current line. Re-run passed.
Watch: no video for this one yet.
AuthorCorey Leon