I’ve been running prompting sessions with people on my team.

The format is dead simple. I ask them: “What do you want done?” They give me a messy answer. Then I show them how to turn that into a question good enough that the answer practically writes itself.

Think Jeopardy. You know the answer you want. Now work backwards to the question that gets you there.

The difference is wild. Someone starts with “I want to understand our deployment pipeline.” That’s a wish, not a prompt. Fifteen minutes later they’re writing: “Walk me through each step of our CI/CD pipeline from commit to production, flag the steps that take longest, and suggest where we could parallelize.”

Same person. Same tool. Completely different output.

The thing nobody tells you about prompting is that it’s not a writing skill. It’s a thinking skill. The prompt is just the artifact. The real work happens when you force yourself to be specific about what you actually need.

No course teaches this. No cheat sheet covers it. You learn it by sitting next to someone who asks you “okay but what specifically?” until your vague request becomes a sharp question.

That’s the whole trick. There is no trick.