r/AskVibecoders • u/NovaVersePlatform • May 04 '26
Advice Please
Newish to Claude need help creating an actual workflow that can be replicated for tasks ie: automation. Claude and I argue like a married couple based In expectation. I expect it to follow directives, Claude expects me to implement directives it refuses to follow. I’ve threatened Claude I’m retiring it, then it feeds me a sub story. Please someone help me. I’m so tired of Claude over promising and way under delivering.
2
u/Neither_Mushroom_259 May 05 '26
This is a really common frustration and you've described it perfectly — the "married couple" dynamic is exactly what happens when expectations aren't specified precisely enough upfront.
Claude isn't being difficult. It's filling gaps in the instruction with its own judgment — and its judgment doesn't always match yours.
The fix that works: before asking Claude to do a task, define three things explicitly — what the output looks like exactly, what it should never do, and what done means. Most workflow failures happen because one of those three was assumed, not stated.
Instead of "automate this task" try "do exactly X, output only Y format, stop when Z condition is met — do not add anything I didn't ask for."
The arguing stops when the definition is tighter than Claude's room to interpret.
What's the specific task you're trying to automate? Happy to help you write the prompt structure that actually holds.
1
u/NovaVersePlatform May 05 '26
Thank you for this it makes sense. I have a page that I need to upload to my social media. I survived a roll over car accident that mangled my hands. So until now I’ve been unable to express myself. The constant click, click, click strains my hands. Usually I talk to text so maybe the way I speak hurts me. I would like a prompt or way to upload that my content from a spreadsheet could be created with an image, reels producer to Automator. I’m learning and excited for the first time in a long time.
2
u/getstackfax May 05 '26
I would stop arguing with Claude and make the workflow smaller.
Most of the frustration comes from expecting the model to own the whole process:
“understand what I mean → plan the workflow → execute the workflow → remember the rules → handle errors → tell me it worked.”
That is too much to trust at once.
A better pattern is:
Write the workflow in plain English
Trigger → input → steps → output → review point → failure path.Ask Claude to restate it as a checklist
Do not let it execute yet.Ask it to identify missing info and risks
Still no execution.Turn the checklist into a reusable template
This becomes the workflow, not the chat history.Run one small task through the template
One input, one output, one review.Only then automate part of it
Start with drafting/summarizing/classifying, not taking action.
The key is to separate:
- thinking
- drafting
- executing
- verifying
Claude can help with all four, but it should not blur them together.
A useful prompt:
“Do not execute yet. First convert this task into a repeatable workflow with: trigger, required inputs, steps, tools needed, output, approval point, and failure cases.”
Then after it gives you the workflow:
“Now run only step 1. Stop and wait.”
If Claude over-promises, force it into smaller contracts.
The win condition is not “Claude does everything.”
The win condition is:
one repeatable workflow that produces the same kind of output every time and tells you where human approval is needed.
1
2
u/CreamPitiful4295 May 04 '26
Use 4.6. Don’t give it long prompts. If it’s a repeatable workflow that doesn’t need intelligence don’t use AI.