Turn a weekly task into a repeatable workflow
One task, five steps, and you never start from zero again.
You have a task you do every week. Same shape every time. You pull some numbers, write the same kind of email, format the same report, summarize the same meeting. It takes 30 minutes. Sometimes an hour. You’ve done it so many times you stopped noticing how much of your week it eats.
That task is where AI earns its keep.
Most people use AI like a smarter search box. They ask a question, get an answer, close the tab. Useful, but it disappears the second you walk away. You start from zero next week.
This article is about the other way to use it. Build the task once. Reuse it forever.
Why repeat tasks are the right place to start
A one-off question saves you a few minutes once. A weekly task saves you those minutes every week, for as long as you keep the job.
Do the math on something you do 50 times a year. If a task takes 40 minutes and you cut it to 10, you got 25 hours back. That’s three full workdays. From one task.
The trick is that you only have to set it up well one time. After that, you’re reusing your own work.
The five steps
Here’s the whole method. I’ll walk through each one with a real example after.
Pick one task you repeat
Write down how you do it now
Turn those notes into a prompt
Run it and fix what’s wrong
Save it where you’ll find it again
That’s it. No code. No special tools. Just a clear prompt you keep.
Step 1. Pick one task you repeat
Look at your week. Find something you do on a schedule that follows the same steps each time.
Good candidates: a weekly status update, a summary of customer feedback, a recap of a recurring meeting, a first-draft reply to a common type of email, cleaning up notes into something readable.
Pick the one that’s boring and predictable. Boring is good here. Boring means the steps don’t change, which means AI can follow them.
Skip anything that needs your judgment to be different every time. Save those for later. Start with the task you could almost do in your sleep.
Step 2. Write down how you do it now
Before you touch AI, write out how you actually do the task. Plain words. The way you’d explain it to a new hire on their first day.
Say you write a Monday update for your team. Your steps might be:
Pull the three biggest things that happened last week
Note what’s blocked and who’s blocking it
List what we’re focused on this week
Keep it under 200 words
Friendly tone, no corporate speak
That list is the whole job. You just didn’t realize you had it memorized.
This step matters more than people expect. AI can’t read your mind. If you skip the thinking and just say “write my Monday update,” you’ll get something generic. The notes are what make it yours.
Step 3. Turn those notes into a prompt
Open Claude.ai. That’s the chat app, in your browser or the Claude app on your phone. You type, it replies. It’s the one I teach on here and the right place to start.
One quick note, because the names trip people up. Anthropic makes three things: Claude.ai is the chat, Claude Code is for software developers, and Claude Cowork is a desktop tool that does work on your files for you. For this, you want Claude.ai. Ignore the other two for now. We’ll get to Cowork later in the series.
Now hand it the notes. Tell it what you want, give it the steps, give it the raw material.
A prompt for the Monday update might look like this:
You’re helping me write my weekly team update. Here’s how I write it:
Lead with the three biggest things from last week
Call out what’s blocked and who owns the unblock
List this week’s focus
Under 200 words
Warm, plain, no corporate speak
Here are my rough notes from this week: [paste your notes]
Write the update.
See what happened. Your steps from Step 2 became the instructions. You’re not asking AI to guess your style. You’re telling it.
Step 4. Run it and fix what’s wrong
Run the prompt. Read what comes back. It won’t be perfect the first time.
Maybe it’s too formal. Maybe it buried the blocker. Maybe it ran long. Tell it what to fix, in plain words:
“Cut it to 150 words. Move the blocker to the top. Drop the last sentence.”
Do that two or three times. Each fix teaches you what to add to the prompt so you don’t have to correct it again next week. When the output is good with no edits, your prompt is done.
This back-and-forth is the work. Ten minutes now saves you the same ten minutes every week after.
Step 5. Save it where you’ll find it again
Here’s where most people lose the leverage. They build a great prompt, then lose it in a chat history they never open again.
Save the finished prompt somewhere you’ll actually look. A note titled “Monday update prompt.” A doc of your best prompts. Pinned somewhere obvious.
Next Monday, you open the note, paste this week’s rough notes, run it. Two minutes instead of thirty.
That’s the whole point. You did the thinking once. Now you reuse it.
Try this today
Pick one task. Just one. The most boring repeat task on your plate.
Run it through the five steps in Claude.ai right now. Don’t aim for perfect. Aim for a prompt that’s good enough to use again next week. That’s your first nugget, and you can do it free in your browser before lunch.
Then take it one step further
Once that prompt works, you don’t have to keep opening Claude and pasting into it. You can hand the whole thing off.
This is where Cowork comes in. Cowork is the desktop version of Claude that does work on your files for you, not just in a chat. Set it up once, give it your context in a short back-and-forth, and ask it for a morning brief. You can build your Monday update right into that brief, or make it daily.
Then every morning you open one file and the work is already done. The update you used to write, sitting there, finished, before you’ve had your coffee.
That’s the real leverage. You build the prompt once in chat to learn how it works. Then you let Cowork run it for you on a schedule. Same thinking, zero ongoing effort.
Start with the prompt today. Graduate it to a brief when you’re ready.
LavaHopper teaches non-engineers how to put AI to work. More at lavahopper.ai