Different from an error message — this is about a task that produces a vague, circling, or repeatedly-wrong result. Usually an instructions problem, not a tool problem. Here's how to actually unstick it.
If you can't describe the finish line clearly, that's usually the real problem — not the tool struggling, but the task itself being too broad or ambiguous to execute cleanly. Narrow it before trying again.
Repeating an ambiguous request tends to produce another ambiguous result — nothing about the situation changed. Add the specific detail that was actually missing the first time instead of trying the same words again.
A narrower, more specific request almost always produces a clearer result than a broad one. If a whole feature feels stuck, ask for just the first piece of it — often that alone resolves the ambiguity that was causing the stall.
"Format it like this" with a real example is more specific than describing the format in the abstract. A concrete reference point removes a whole category of ambiguity that words alone sometimes can't.
The free guide covers a first real workflow — the fastest way to build the scoping habits that prevent this.
Get the Free Guide →An error message is a technical symptom to fix. Getting "stuck" here means the task itself is unclear or too broad — the fix is better instructions, not a technical debugging step.
Break the task into a smaller, more specific piece and try again — a narrower request almost always produces a clearer result than repeating the same broad one.
Not without changing something — repeating an ambiguous request tends to produce another ambiguous result. Add the specific detail that was missing instead.
If you can't describe what "done" looks like in one sentence, the task is probably too big for one request — that's usually the real signal, more than any specific error.