One builder tested 40 AI workflow ideas this year and killed 35 of them within a week. The five that survived have been running every single week for six months straight. The Redditor u/Professional-Rest138 shared the whole setup in r/PromptEngineering, and the pattern behind what survived is worth stealing.
The common thread across all five: each one replaced a recurring task that used to eat 30 minutes or more. None of them are clever. All of them run on autopilot now.
The Five Prompts
The Proposal Generator (saves ~2 hours per proposal)
Turn these notes into a formatted Word doc proposal ready to send today.
Notes: [dump everything]
Client: [name]
Price: [amount]Sections: Executive summary, problem, solution, scope, timeline, investment, next steps. Formatted .docx. Sounds human.
Two constraints do all the work: “ready to send today” sets the tone, and “sounds human” keeps it out of corporate-speak territory. If you send proposals by email instead of file attachment, swap “.docx” for “a clean HTML email” and the same structure applies.
The Meeting Processor (saves ~30 minutes per meeting)
Here are my rough notes: [paste]
Attendees: [names]Give me:
1. Half-page summary
2. Action items table (task, owner, deadline)
3. Follow-up email ready to send to all attendees
Three deliverables, one input. The follow-up email coming out pre-written is what makes this one stick. Most meeting notes die in a doc somewhere. This forces them into a sent email.
The Content Repurposer (one piece becomes five)
Here’s a piece I wrote: [paste]
My voice: [describe]Repurpose into:
– LinkedIn post (200-300 words)
– Three standalone X posts
– Email to my list (150 words)
– Instagram caption
– One-paragraph summarySame voice across all. No AI clichés.
“No AI clichés” and “same voice across all” are doing the heavy lifting here. Without those constraints, you get generic filler that sounds like every other AI-written post. With them, the repurposed pieces actually sound like you.
The Friday Review (10 minutes that kills Sunday-evening anxiety)
Here’s what happened this week: [brain dump]
Numbers: [whatever you track]Give me:
– What actually went well and why
– What didn’t work (honest, no softening)
– Top 5 priorities for next week ranked
– The single clearest thing I should change
“No softening” is the most important instruction in this prompt. Without it, the output finds something nice to say about everything. If you track numbers in a spreadsheet, paste them directly instead of summarizing. More specific input, more specific output.
The End-of-Day Reset
Today’s notes: [dump everything from today – tasks done, conversations had, things you’re carrying into tomorrow]
Tell me:
1. What I should write down before I forget
2. Anything I committed to that I haven’t actioned
3. The one thing I should sleep on rather than decide now
4. Tomorrow’s first hour – what’s on it and why
The original poster says this one surprised them most. Question 3 is the one that matters: separating “decide tonight” from “sleep on it.” That single question prevents a lot of bad late-evening calls.
Why These Five and Not the Other 35
The sharpest take came from the comments. u/mm_cm_m_km wrote:
“The five that stuck all collapse a recurring decision into a fixed prompt template plus a fresh data dump. The 35 that failed probably mixed those two so each run was bespoke.”
When the structure is locked and only the input changes, you stop thinking about the prompt. That’s when it becomes genuinely automatic. An automation you have to redesign each time is not an automation.
u/ultrathink-art added the other piece: fresh context every run. Claude resets between sessions. These prompts work because they’re built for that reality, not against it. Workflows that try to maintain state across sessions tend to fall apart by month three.
🗂 Use Cases
These aren’t limited to solo operators. The same pattern transfers if you’re:
- Sending weekly client updates where consistency and speed matter
- Running a content calendar where one piece needs to become five formats
- Managing proposals or scopes of work more than once a month
The proposal generator alone is worth fifteen minutes of setup time.
Prompt of the Day
The Friday Review. Run it before you close your laptop this week.
Here’s what happened this week: [brain dump]
Numbers: [whatever you track]Give me:
– What actually went well and why
– What didn’t work (honest, no softening)
– Top 5 priorities for next week ranked
– The single clearest thing I should change
The original poster’s advice: if you only set one of these up this week, make it this one. The first time you close your laptop on Friday without carrying the week into your weekend, the whole approach clicks.
Try One This Week
Find the full thread and community reactions in r/PromptEngineering under u/Professional-Rest138’s post. Start with the Friday Review. The rest can wait until that one becomes habit.
Frequently Asked Questions
Q: Why do some Claude automations stick and others get abandoned?
The five that stuck collapse a recurring decision into a fixed prompt template, then feed fresh data into it each run. The 35 that failed mixed template with decision-making , you rethought the prompt each time. Once the template stabilizes, friction disappears and it becomes routine.
Q: Would local models like Gemma-4 work better and save money?
They handle basic template-filling fine, but Claude shows value when quality matters , repurposing content across formats, writing that sounds human, capturing nuance in meeting notes. If cost is your priority and lower quality is acceptable, local models work. Otherwise, Claude’s subscription pays for itself on these recurring tasks.
Q: Can you automate these workflows on a schedule?
Manual triggers are fine and actually more reliable to start. If you want automation, wire them into a shell script, Reminders app (Mac), or a background agent that fires on schedule with pre-loaded context. The key is each run needs fresh context , don’t try to maintain memory across sessions.
Q: How do you maintain context across multiple Claude sessions?
You don’t , that’s the stability secret. Each Claude session resets to zero. The automations that stick dump fresh context every run (notes, attendees, numbers). The ones that fail try to maintain cross-session state and break when context gets stale.
Q: Aren’t these just fancy templating? Where’s the AI value?
They’re template-filling with adaptive intelligence. Static templates can’t reshape your data to match your voice, adapt content across formats, or capture nuance in a chaotic week. That’s where Claude adds value , the intelligent adaptation layer.
I’ve been running Claude like a part-time employee for six months. These are the only automations that actually stuck.
by u/Professional-Rest138 in PromptEngineering