How to Convert a Chat into a Coherent First Draft

The problem

You’ve finished a roleplay chat. The story works. The characters are vivid, the dialogue is strong, the scenes build to a satisfying arc. But it’s a chat log, not a story. The format is alternating messages between two participants. The perspective is second person. Action is wrapped in asterisks or implied by the chat interface. Internal monologue is mixed with dialogue with no clear separation.

You paste the chat into your AI and say: “Turn this into a story.” The model produces a summary. Or it picks the most dramatic moments and skips the rest. Or it changes the dialogue to “improve” it. The story you lived through in the chat is gone, replaced by something that happened to someone else.

The problem is that “turn this into a story” doesn’t tell the model what to preserve. The model doesn’t know which details are load-bearing, which lines of dialogue are essential, and which action beats are the story’s spine. It guesses. It guesses wrong.

Why this prompt is different from the revision prompt

The revision prompt takes a draft that’s already in story form and polishes the prose without changing the story. The roleplay-to-story prompt takes text that isn’t in story form and converts it into story form while preserving the story. It’s closer to a rewrite than a revision, but it’s a constrained rewrite. The constraint is: the story beats, the details, and the dialogue survive the conversion. The format changes. The content doesn’t.

The key difference is the preservation instruction. In the revision prompt, you tell the model not to change story choices. In the roleplay-to-story prompt, you tell the model not to lose story content while changing the format entirely.

The five-part template

Same structure as the start-writing and revision prompts. The role shifts to adapter. The task shifts to conversion. The constraints stay the same. The format changes to reflect what a story draft looks like versus a chat log.

1. Role

Tell the model it’s converting a chat into prose. “You are my fiction-writing collaborator” is the right role. Not editor, not rewriter. Adapter. The model is adapting one format into another while preserving content.

2. Context

Character profiles, any planning documents you have for the roleplay, and the chat log itself. If you have a treatment or outline for the roleplay, include it. If the roleplay was improvised with no planning documents, just the character profiles and the chat.

3. Task

This is where the conversion happens. The model needs to:

1. Read the chat and identify the story’s spine: the major beats, the turning points, the arc
2. Identify which lines of dialogue are essential and which are filler
3. Identify which action beats are load-bearing and which are atmosphere
4. Convert second person to third person
5. Convert chat messages into scenes with dialogue, action, and interiority
6. Weave the beats into a coherent narrative with scene breaks, transitions, and pacing

The silent identification step is critical here. Before converting, the model needs to understand what the story is, not just what the chat says.

4. Constraints

Same compressed style reminders. The accumulation principle is especially important because chat logs tend to repeat the same physical descriptions and emotional beats across multiple messages. The conversion process can amplify that repetition if the model doesn’t watch for it.

5. Format

Tell the model to output a complete first draft short story. Not a summary. Not an outline. Not a cleaned-up chat log. A story with scenes, dialogue, action, and narrative prose.

The copy-paste prompt

[ROLE]
You are my fiction-writing collaborator. Your job is to convert a roleplay chat into a coherent first draft short story. Preserve every major story beat, essential detail, and line of dialogue. Change the format from chat log to prose fiction. Change the perspective from second person to third person. Do not summarize, skip, or condense the story.

[CONTEXT]
Character profiles: [link or paste]
Planning documents (if any): [link or paste]
Roleplay chat log: [paste chat here]

[TASK]
Convert the roleplay chat into a coherent first draft short story.

Before converting, silently identify:
- Who are the characters? What does each one want?
- What is the story's spine? What are the major beats and turning points?
- Which lines of dialogue are essential? Which are filler?
- Which action beats are load-bearing? Which are atmosphere?
- What is the emotional arc of the story?
- What is the setting, and how does it change across scenes?
- Where does the story break into natural scenes?

Then convert:
- Change all second person perspective to third person. "You walk into the room" becomes "He walks into the room" or "She walks into the room" using the character's name.
- Convert chat messages into scenes with dialogue, action beats, and interiority. Each character's messages become their dialogue, actions, and thoughts.
- Weave the beats into a coherent narrative with scene breaks, transitions, and pacing appropriate to prose fiction.
- Preserve the essential dialogue. You may tighten lines for prose rhythm, but do not change the meaning or intent of any line.
- Preserve the major story beats and finer details. If a character notices something specific, keeps it. If a detail establishes character or setting, keep it.
- Add connective tissue between scenes where the chat jumps. The chat may skip transitions that a story needs.
- Convert internal monologue from chat format (parenthetical, bracketed, or implied) into narrative interiority.

[CONSTRAINTS]
- No em dashes. Use periods, commas, or restructure.
- No triple-beat fragments or staccato verb sequences.
- No vague interiority. Name what happens or show it through behavior.
- No anthropomorphized silence or atmosphere.
- No default physical tells. Use character-specific behavior.
- Accumulation principle: any pattern appearing more than twice in a scene gets rewritten on the third instance.

[FORMAT]
- Output a complete first draft short story in third person prose.
- Use scene breaks (*** or #) between scenes.
- Start scenes with character presence, action, decision, or pressure.
- End scenes on action, decision, rupture, consequence, interruption, or a concrete image that changes meaning.
- After drafting, perform a hidden revision pass. Search for the patterns above and rewrite them. Do not explain the revision unless asked.
- Give me only the polished first draft.

How to customize per conversion

The chat log: Always. Each chat has different problems. Read your chat before sending it and add specific notes about what you want preserved. For example: “The scene where Luke touches his stomach in the tub is the emotional center. Don’t lose the sensory details there.”

The task section: Often. If the chat has specific structural issues, note them. “The chat jumps between three locations with no transitions. Add connective tissue.” Or “The chat has a long section of back-and-forth dialogue that should be compressed into a single scene.”

The constraints section: Sometimes. Chat logs tend to have specific patterns that differ from drafts. Roleplay often uses the same physical description repeatedly across messages. If you notice this in your chat, add: “The chat repeats [specific description] across multiple messages. Vary the language or consolidate references.”

The format section: Rarely. The output format stays the same: a complete first draft short story.

The role and context sections: Almost never. These stay stable across conversions.

Common mistakes

Saying “turn this into a story” without preservation instructions. The model produces a summary or picks the most dramatic moments. It doesn’t know which details are load-bearing. Tell it explicitly: preserve every major beat, essential detail, and line of dialogue.

No silent identification step. The model starts converting without understanding the story’s spine. It transcribes the chat into prose format without identifying which beats matter. The result reads like a cleaned-up chat log, not a story. Always include the identification step.

Changing dialogue meaning. The model “improves” dialogue by making it more dramatic or more articulate. The character’s voice is lost. Tell the model it may tighten lines for rhythm but must not change meaning or intent.

Losing details in scene transitions. The chat jumps between moments. The model follows the jumps and skips the connective tissue. The story feels fragmented. Tell the model to add transitions where the chat jumps.

Not specifying third person. The model keeps the chat’s second person perspective or switches between perspectives. Always specify the target POV explicitly.

Including the full style guide. Same problem as the other prompts. Token waste and attention splitting. The compressed constraints section is sufficient for a first draft conversion. The full style guide can be applied in a separate revision pass using the revision prompt.

The two-step workflow: convert, then revise

For the best results, use the roleplay-to-story prompt and the revision prompt in sequence:

1. Convert: Use the roleplay-to-story prompt to turn the chat into a coherent first draft. The focus is on preserving content while changing format.
2. Revise: Use the revision prompt to polish the first draft. The focus is on improving prose without changing the story.

These are two different operations with two different prompts. Don’t try to do both in one pass. The conversion prompt preserves content. The revision prompt polishes prose. Combining them splits the model’s attention and produces neither a faithful conversion nor a clean revision.

What to include from the chat

Include the full chat log if possible. If the chat is very long, include the most relevant sections and note what was cut. The model needs the full conversation to identify the story’s spine and preserve the beats.

If your chat includes system messages, character card descriptions, or formatting metadata, include them. The model can use this information to understand character voice and setting. If the chat uses asterisks for action, include them. The model will convert them into narrative prose.

If the chat includes out-of-character notes or planning discussion, you can include these or strip them. Including them gives the model context about the story’s intent. Stripping them keeps the focus on the in-character content. Either works. If you include them, add a note: “OOC notes are included for context. Do not include OOC content in the story.”

---

This guide is a companion to The Start-Writing Prompt and The Revision Prompt. Use the chat-to-story prompt to convert a chat or character roleplay into a first draft. Use the revision prompt to polish it. For the full style guide covering banned constructions and the accumulation principle, see our companion article.