Message Input and Slash Commands on Reply

[k9lego]

Description
Slash commands Message input would be very useful for a system that users report a message to the moderators. It would function something like this:
You would either reply to a message and do a slash command, and if one of the arguments was a Message, it would populate that with the message ID. Note that this should also accept a Message ID (though it might only search that channel for the specific message ID for simplicity).

Why This is Needed
I would say this is a lower-priority request, as some of the features on the master-list are needed more than this. However, a message input would be very helpful for systems such as reporting. It also feels strange not being able to use slash commands when replying to a message, and "role"/"user"/"channel" all three arguments, so feels like it's missing "message".

Alternatives Considered
A reaction of a specific emoji works too, but that really is not ideal because it requires you to listen to all reactions, and sometimes someone might react with that emoji for a different purpose and accidentally trigger the bot.

Additional Details
I can see the goal of slash commands is to eventually make message data a privileged intent. I respect that, however a system like this would allow a user to give the bot only the specific message it needs. I'm sure there are a few other solutions, but IMHO this feels like the cleanest.

[Headline]

I do really need this support for slash commands to function properly with my bot.

I manage a bot that's able to compile code, and I'd really like it so users can reply to messages with codeblocks with a slash command. That way the bot can view that message content. I think it'd be pretty straightforward for application command interactions to have an optional reply field.

[QuantumToasted]

Just so you are both aware, message-based application commands already exist.

While I'm not going to try to convince anyone that they are a full-blown replacement and solution for your issues at hand, you can easily turn a message command into a more customizable command by following up on that interaction with, say, an ephemeral message which includes components such as buttons or a drop-down to extend functionality or provide customization. Here's an example for a bot in a server I manage:

[Headline]

Hello, thanks for your message!

I feel that this issue comes down to the UX experience of the application. While I believe we're both aware that message commands exist, that doesn't really mean that replying to a message with slash commands isn't intuitive for users on the Discord platform.

[erkinalp]

Message commands do not accept additional arguments, whereas slash command replies could.