[Feature]: Command for sending ''In discussion'' template response to sender (DevC)

Problem or Use Case

Due to the amount of messages DevC gets, it's unreasonable to expect them to be handled immediately. Some take a bit longer as a result, and it would be nice that once a non-UWC message enters discussion phase, that one of the members can type a command that automatically sends a response that it's being discussed. This could eventually be brought over to other teams as well.

Proposed Solution

Add an "in progress" command that sends the following template. {user} is grabbed from the message.

Hello {user},

Your message has been received well and we are currently discussing it within the team. Sit tight, we'll try to get back to you as soon as we can!

-DevCompliance

Alternative Solutions

The command could generate the template and then someone on the team can send it instead. Currently a template could be pinned somewhere, but it would cost too much effort to find this pin every time, then copy and send, while a command could automate it much quicker.

Command Type Preference

Slash command (/) - Preferred

Feature Scope

Team members only

Usage Examples

/InDiscussion
/InDiscussion type:Subset Request

Additional Context

One possible complaint that could come up is that the response would feel very automated and generic. A possible alternative is to create a bunch of different templates, and then let RAbot grab a random one from the pile while still being applicable to whatever is sent.

Likewise, I included with Usage Examples a type; this could make the responses more natural to whatever is sent, e.g. Subset Requests or Set Approval Requests.

Checklist

• I have searched existing issues to ensure this feature hasn't been requested
• This feature would be useful to multiple users, not just me
• I have provided clear use cases and examples

Start at the slash-command entry point and review how existing commands identify the sender and enforce team-member access. Implement the /InDiscussion behavior described in the issue, including the user name and optional message type, then verify that it sends the specified template only for authorized team members.