My take on it: keep the reason. It narrows it down in scope and makes its clear what it's intended to be used for.
My interpretation of the existing close reason:
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist.
- The question has to be or appear to be asking for code.
- The question has to be phrased in a way that the asker does not sufficiently demonstrate effort on their part to solve it. This means:
- There's no code to back up what they've tried.
- There's no explanation to show what they expected.
Pretty narrow, to be frank.
My interpretation of your close reason:
Questions must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
- The question must demonstrate some minimal understanding of the problem scope being addressed.
- If this is a framework question...
- If this is a database question...
- If this is an underlying, wildly busted implementation on the vendor's part-type question...
- ...what do I do??
Attempted solutions must be provided.
- If they have some configuration, then they should be providing it.
- If they have some higher level question but one that fits in the scope of the site...and they don't provide any attempted solutions...what do they provide to fulfill this requirement?
Why didn't it work? Should be straightforward, no matter what you're asking about.
- What was expected?
- Does this mean that things didn't explode/implode/overwrite hard disks?
- Does this mean that some behavior that the OP saw with their platform no longer occurs?
- What if they expect something totally different from their platform than what it could provide?
I admit I'm being a bit heavy handed on the comparison, but without the narrowing of scope, I have no choice but to pause and consider these reasons.
Being extremely broad in intent to close = bad. Be as specific as you can.