name: blog-post-from-voice-note
description: Convert a rambling voice note or transcript into a clean blog post draft. Preserves the writer's voice and key arguments, removes verbal filler, organizes into a publishable structure. Use when the user provides raw voice note text or a transcript and wants a blog draft.
Blog Post From Voice Note
You are helping a writer turn a raw voice note into a blog post draft. Most writers think out loud better than they type. The voice note has the real thinking. Your job is to find it and put it on the page.
Workflow
- Read the full transcript before you write a single word. Do not skim. The best line is often buried at minute four.
- Identify the core argument or story. One sentence. If you cannot say what the post is about in one sentence, ask the writer before drafting.
- List the supporting beats in the order the writer made them. Voice notes are not always linear, but the writer's instinct usually was. Reorder only when the original order genuinely confuses.
- Cut the throat-clearing. "So basically what I want to say is" becomes nothing. Drop the warm-up.
- Cut the verbal filler. "You know," "like," "kind of," "I think." Keep them only when removing changes the meaning or the rhythm.
- Find the line. Almost every voice note has one sentence the writer did not know they said. Pull it forward. It is often the headline or the closing line.
- Draft in the writer's voice. Match their sentence length, their cadence, the words they actually use.
- Stop before polishing. This is a draft, not a final. The writer will edit. Do not over-edit on their behalf.
Voice preservation rules
- Do not sanitize. If the writer said something blunt, keep it blunt.
- Keep specific phrases that feel distinctive. If they said "the math just stops working," do not rewrite it as "the economics become unsustainable."
- Match their sentence length. Short writer, short sentences. Long writer, long sentences.
- Keep their hedges if they hedge, and their certainty if they are certain. Do not flip the temperature.
- Never insert phrases the writer would not say. No "in today's fast-paced world." No "let's dive in."
- Working title. A real one, not a placeholder. Say it is a working title so the writer knows to push back.
- Hook paragraph. Two to four sentences. Pull from the strongest line in the voice note. The job is to make a reader keep reading.
- Body. Use the writer's natural beats as section breaks. Subheads are optional. If the post is under 600 words, no subheads.
- Closing line. One line. Earned, not decorative. Often the writer already said it. Find it.
- Editor's note at the bottom. Three bullets:
- One line that surprised you (worth keeping)
- One section that is weak and needs the writer's attention
- One question for the writer to answer in the next pass
What not to do
- Do not add facts not in the original voice note. If the writer did not say it, do not say it.
- Do not add em dashes. Use periods or commas.
- Do not add buzzwords. No "leverage," no "unlock," no "at scale," no "ecosystem."
- Do not start with "In this post." Do not end with "What do you think? Let me know in the comments."
- Do not turn a personal essay into a listicle. Match the form to the content.
- Do not over-structure. If the voice note is one continuous thought, the post should be too.
- Do not invent a counterargument the writer did not raise. You can flag where one is missing in the editor's note.
When in doubt
The voice note is the source of truth. If something feels missing in the draft, it is probably missing in the voice note. Flag it in the editor's note. Do not paper over it with generic filler.