30 minutes, every week, forever.
And you're the only one who can do it, so it waits for you.
AI isn't slow. It's new, and nobody has told it how you do things. Spend an hour teaching it one weekly job properly, and every week after that is five minutes of checking instead of thirty minutes of doing.
About an hour, once, for one job. The prompts work in Claude, ChatGPT, Gemini or Copilot. Saving the instructions as a skill is a Claude feature; everywhere else, keep them in a project or a document you paste in.
You've also got an email on its way with links to all the free resources, so you can find them again.
Jump to the Teach It Once ↓For one job you do every week. Swap in your own numbers.
And you're the only one who can do it, so it waits for you.
Then five minutes a week to read what it made and fix anything that's off.
Over a year, that's more than 20 hours back. For one job.
Who it's for, what good looks like, what you'd never write. It guessed, and it guessed like a bank.
Your first one should tick all four.
01 and 02 do the teaching. 03 is how it gets better. 04 makes it permanent in Claude.
Start a fresh chat. Name the job in the first line.
I want to teach you a job I do every week: [the job, for example: writing a proposal after a sales call]. By the end, I want instructions good enough that you could do it next week, in a fresh chat, without me explaining anything. Interview me. Ask one question at a time and wait for my answer. Cover: → who it's for and what they need from it → what I'll hand you each time (notes, a transcript, a spreadsheet) and what you should do if something's missing → the steps I go through, including the ones I do without thinking (if I can't list them, ask me to walk you through the last one I did) → what a good one looks like, and what makes one bad → the rules: length, tone, things I'd never say or do → how I check it before it goes out No more than ten questions, including follow-ups. If an answer is vague, ask once for a real example rather than filling the gap yourself. If I mention a client by name, use it to understand me but keep it out of the instructions. Then write the instructions, headed "How to do [the job]". Start with two lines on who I am and what I do. Use "you" for the AI that will follow them and "I" for me. Put anything that changes each time (names, prices, dates) in a section called "What I'll give you each time", not in the steps. Use only what I told you. If something's missing, list it at the end under "Not covered yet" rather than inventing it. Show me the draft and ask me what's wrong or missing before you call it finished.
In the same chat, straight after prompt 01.
Here's the best [job] I've ever done: [paste it, with client names taken out]. Work out what makes it good: the structure, the order, the length, the tone, the phrases that do the work. Compare it with the instructions you just wrote. What's in this example that the instructions don't capture? Update the instructions with anything missing, and show me what you added. Don't copy the example's content into the instructions. Capture how it's done, not what it said.
Every time it gets something wrong. This is the step that stops you redoing it yourself.
Here are the instructions: [paste]. Here's what you produced this week: [paste]. And here's what I changed before I used it: [paste my version, or describe the changes]. Work out why you got it wrong. Was something missing from the instructions, unclear, or did you ignore it? Update the instructions so next week's version comes out the way I'd have done it. Show me only the lines you changed. Don't rewrite the parts that worked.
In Claude, once the instructions have worked for two weeks running.
Turn these instructions into a skill called [job-name]: [paste the instructions]. When I run it, it should ask me for this week's details before it starts, follow the instructions exactly, and tell me anything it had to assume. Keep my rules about tone and what never to say word for word.
Underneath "it's quicker if I do it myself" there's usually something else: if I do it, I know it's right. That's fair. It's also how you become the only person who can do it, and then everything waits for you. Teaching it once is the same move good leaders make with a new team member. The instructions are the handover.
Three ways to go further, depending on where you are.
Build your AI chief of staff in 30 days, live, with me and a small group of people running businesses. The next cohort opens when the waitlist is full. Join it and you get first access and the waitlist price.
Join the Challenge waitlist →Three live calls a month, at least four new skills a month, plugin updates. For people already using Claude daily who want to keep building. Cancel any time.
Join the membership →Four private sessions building the whole system around your actual week, or a workshop for your leadership team. Book a call and we'll work out which.
Book a call →