You are viewing v1 of 1. Go to the current version · All versions

Turn rough notes into a blog post

Convert scattered notes into a structured, readable blog post in your voice, without padding or invented facts.

Change note: Initial version

Prompt

Turn my rough notes into a blog post.

Topic: {{topic}}
Reader and what they care about: {{audience}}
Goal of the post: {{goal}}
Voice: {{voice}}
Length: about {{word_count}} words
Search phrase to include naturally, if any: {{keyword}}

My notes (messy, in any order):
{{notes}}

Instructions:
- Use only the facts and opinions in my notes. If you need a statistic or example that is not in the notes, leave a bracketed placeholder like [add data: ...] instead of inventing one.
- Start with a first paragraph that states the problem or the surprising point. No "In today's fast-paced world".
- Use short paragraphs, descriptive subheadings and concrete examples. One idea per section.
- End with a takeaway and one clear next step for the reader.
- Avoid filler phrases, rhetorical question piles and forced enthusiasm.

Output format: a title, a one-line meta description under 155 characters, then the post in Markdown. Finish with a list of any placeholders I need to fill and any notes you could not place.

Variables

  • {{topic}}Topictext

    Default: Why small teams should write down decisions

  • {{audience}}Readertext

    Default: Startup founders and team leads with no formal process

  • {{goal}}Goaltext

    Default: Convince readers to start a simple decision log this week

  • {{voice}}Voiceselect

    Options: Conversational and practical, Authoritative, Playful, Plainspoken and honest, Academic but readable

    Default: Conversational and practical

  • {{word_count}}Word countnumber

    Default: 700

  • {{keyword}}Search phrasetext

    Default: decision log

  • {{notes}}Your noteslong

    Default: - we kept re-arguing the same pricing choice every quarter - a one-page doc per decision: context, options, choice, date - took 10 minutes each, saved hours - new hires onboarded faster - don't aim for perfect, aim for findable

    Bullets, fragments, anything

Example output

Title: Write Down Your Decisions (It Takes Ten Minutes)
Meta: A simple decision log stops teams re-arguing old choices. Here is a one-page format you can start this week.

Every quarter, my team re-argued the same pricing decision. Nobody was wrong; nobody could remember why we had chosen what we chose.

## The fix is one page
For each decision, write four things: the context, the options considered, what you chose, and the date. That is it.

## Ten minutes, hours saved
Each entry took about ten minutes. It saved far more by ending repeat debates before they began.

## A bonus: faster onboarding
New hires read the log and understood our reasoning without a dozen meetings.

## Aim for findable, not perfect
[add data: how many decisions you logged in the first quarter]

Start this week: pick the last decision you argued about twice and write it up.

Placeholders to fill: one data point in "Aim for findable".

Notes

The placeholder rule keeps the draft honest. Add your own anecdotes in the notes for a post that does not read like generic content.