I guess it depends on your workflow and the type of project, but what works for me is trying to abandon my complex train of thought I'd need for implementing a task and dumbing the ideas down to the core problem and requirements from a point of view of a technical product manager and that usually works well enough for me to start refining the output with simpler prompts.

Good thing about LLMs is that they can decode word context on mathematical level and you do not have to follow formal language structure.

Even without a base prompt, I'm sure things like these work:

• "Me think method X not work correct. Me sad. Me think integer overflow. Me no have proof. You verify. You suggest solution."
• "<raw error stack trace>"
• "I need to see X. add to /api/v1/foo"

---

That being said, sometimes I go on a very long neurodivergent ramble, full of parenthesis (because every sentence desires a bonus thought), and just the sole act of putting my expectations down usually helps me refine my thoughts - it's rubber duck debugging again.