Make giving clear context more prominent in "how to ask a good question"

By far the most common fault I encounter in reasonably good attempts at asking for help here is something I've seen called "the xy problem", where someone has encountered a situation, has a method for dealing with it, and is asking for help on how to implement that method but their real problem is in their choice of method.

How to ask a good question does say

Introduce the problem before you post any code

In the body of your question, start by expanding on the summary you put in the title. Explain how you encountered the problem you're trying to solve, and any difficulties that have prevented you from solving it yourself. The first paragraph in your question is the second thing most readers will see, so make it as engaging and informative as possible

but I think that could be improved. The heading should certainly strip "before you post any code", newbies who aren't posting code, i.e. they're having trouble using tools not writing code, will just skip right over it. And that last sentence there? Move this section above the bullet points that currently precede it, they don't just apply to the title. Here's my first attempt at an improved version:

Write a question title that summarizes the specific problem

The title is the first thing potential answerers will see, and if the summary there isn't interesting, they won't read the rest. So write the best, most concise introduction you can here (and see below)

Explain the situation that prompted your question

In the body of your question, start by expanding on the summary you put in the title, and be sure to provide enough context that people trying to help you are likely to understand how to proceed. If you're having difficulty implementing the solution to some problem, explain the problem as well as the solution you're attempting and the difficulty you're having. The first paragraph in your question is the second thing most readers will see, so make it as engaging and informative as possible.

In general

• Pretend you're talking to a busy colleague and have to sum up your entire question, one sentence for the title everyone sees and a rewarding paragraph for those that take an interest. What details can you include that will help someone get you out of the trouble you're in? After your first explanation of the situation, subsequent details should include any error messages, key APIs, or unusual circumstances that make your question different from similar questions already on the site.
• Spelling, grammar and punctuation are important! Remember, this is the first part of your question others will see - you want to make a good impression. If you're not comfortable writing in English, ask a friend to proof-read it for you.
• If you're having trouble summarizing the problem, write the title last - sometimes writing the rest of the question first can make it easier to describe the problem.

edit: s/identify your problem/get you out of the trouble you're in/