What is the rationale/criterion on this site for the Too-broad close reason?
I think I have a pretty good handle on close reasons for existing SE sites, and the "too broad" close reason in particular. Because this site breaks with the SE canon by inviting recommendation questions, it may be worth discussing each of the standard close reasons as to a variant meaning for this site before proceeding to Custom close reasons for software recommendations. The too-broad close reason has been discussed with a straw-man example, but here is a real-world case.
The boilerplate text for too-broad mentions that there may be "too many possible answers" or that "good answers would be too long for this format".
Obviously in the context of asking for recommendations, it might well be that the Asker is aware of many possible ways to perform a computer task and wants a first-hand success story to guide their own selection. So this weakens the argument that a Question should not be asked if there are many possible answers.
Likewise the concern that "good answers would be too long" should be lessened for this site. An ideal Answer will treat only one software recommendation, not an exhaustive enumeration of all possibilities or all the steps needed to use a recommended package. It should not exceed the limits of the SE format to identify the package, address the requirements posed by the Question, and make brief remarks about the satisfactory nature of User's own experience with the software.
Of course vague, overly-general or rambling Questions should be closed, but in most cases the "unclear what you're asking" close reason will better suit those cases. So what will be the occasion for using a too-broad close reason on SWRecs.SE?