What happens when someone needs one very specific feature?

Question

I agree with the quality standards that have been outlined so far but I think there's a problem with people understanding the difference between a low quality question and a brief question.

There's a big difference between "I need an IDE." and "I need a plugin for this specific IDE that does this one specific task in this specific way (with examples)." The latter is getting treated like the former either because the reviewer doesn't know the software well enough or because the asker doesn't know enough to provide more information. Either way a terse request for more requirements isn't exactly helpful.

There's plenty of information on what constitutes a good question. Can we get some information on when and how to ask for more information?

Note:

We had this problem on Christianity.SE. It has a lot of the same problems with subjective questions and answers that this site has. Over there we came up with a fairly concise set of guidelines on helpful criticism and I think something similar would help here.

Answer 1

Here is an example of a good question with one feature request that is so specific that others are not needed:

Program to search EULA contracts for problems

We want to make sure that questions are not too broad. However, some tasks are so specific by themselves that other feature constraints are not needed to keep the question from being too broad.

This will always be a judgement call. We can't (and shouldn't) specify a rule that spells out the minimum number of required features for a question. Before voting to close a question for being too broad, ask yourself if it really is too broad, or if you just have that impression because it doesn't have a big feature list.