The X reply brief we wrote so the draft wouldn't pick a fight

Short replies on X leave no room to fix a misunderstanding, so our X guide starts with the instruction you give the draft.

The post in the example is about releasing software. The brief: "Ask whether 'released' means a public launch or an internal test. Keep it neutral and concise. Do not imply that the author made a mistake."

The last sentence is there because a short draft can turn a question into a dig. If what comes back has a joke, an accusation or a claim about your own experience in it, check whether you asked for any of that.

A few other things from the same page:

• The shortest length setting can cut the qualification that made the reply fair. Normal or Long is fine.
• Replying to the original post and replying to someone further down the thread can mean different things. Check who you're answering.
• If the post has a screenshot, video or link, look at it yourself before you say anything about it.
• Saved instructions carry into the next draft. Clear them before you move on.

In ReplyPilot it's /rp in the reply field, pick a length, write what the reply is for, generate, edit, and post it yourself. The rest is in the X reply walkthrough.

ReplyPilot