For an everyday conversation
We're choosing a recipe for dinner. Ask what ingredients I already have, one question at a time. Suggest a dish only after I answer, and keep your replies to two or three sentences.
This gives the exchange a task, a sequence and a length. Your next message should supply an ingredient or preference rather than introduce a different problem. If the reply is too long, adjust that one instruction first.
For a fictional roleplay opening
We are adult archivists sorting a closed museum's last delivery. You have found a clock that is still ticking inside a sealed crate. Describe one detail of the room and ask whether I recognise its maker. Do not write my character's thoughts or decisions.
The setting contains something to react to without prescribing the whole plot. An RPG scene can develop through the next choice instead of requiring a full world history in its first message.
For returning to an unfinished scene
Recap the few facts the next turn depends on. For the museum: The crate is open, the clock is still running, and neither archivist has read the label.
Follow that with the immediate question.
Use memory controls for concise recurring facts and custom instructions for reply style. Neither is a promise that every earlier message is available forever. Update facts when the story changes.
For revising a reply pattern
Change the smallest relevant instruction: less narration, shorter paragraphs or one speaker at a time. Remove contradictions such as asking for both a one-sentence answer and an exhaustive description. Try the next turn before rewriting the character.
Deleting a message removes it from that conversation's model context, so keep anything you still need. If the problem is a failed request rather than the writing, use technical troubleshooting.