ToolSiftToolSift
Back to skills
BeginnerWriting

Turn rough notes into a structured blog post

A workflow for turning scattered notes into a clear article outline, draft, and editing plan without letting AI invent expertise or flatten the author's point of view.

Who it is for

  • Founders, editors, and creators with messy notes.
  • SEO writers who need structure before drafting.
  • Subject-matter experts who do not want to start from a blank page.

Who should skip it

  • Users who want AI to invent the entire argument.
  • Teams publishing regulated advice without expert review.
  • Writers who have no audience, angle, or source material.

Workflow

Step 1

Separate raw material from missing material

Paste the notes and ask the AI to sort them into facts, opinions, examples, open questions, and missing evidence. This keeps the model from pretending your notes are complete.

Example input

Sort these notes into usable points, claims needing evidence, examples, and missing context.

Expected output

A content inventory that shows what can and cannot be drafted yet.

Common failure

The AI starts drafting before identifying gaps.

Human check

Check whether every important claim has a source, example, or clear author opinion.

Step 2

Define the reader and promise

Ask for possible angles, then choose one reader and one promise. A blog post becomes weak when it tries to serve beginners, executives, and technical users at the same time.

Example input

Suggest three article angles for beginner SaaS operators, then recommend one.

Expected output

A single target reader, promise, and article angle.

Common failure

The outline becomes a generic overview.

Human check

Read the H1 and ask whether a real reader would know why to continue.

Step 3

Build an outline with evidence slots

Create an outline that includes what each section must prove, what evidence is needed, and where the notes already support the section. This prevents decorative headings with thin content.

Example input

Create an outline with section purpose, note references, missing evidence, and examples.

Expected output

A reviewable outline with evidence slots.

Common failure

The AI creates a polished but unsupported outline.

Human check

Delete any section that cannot be supported or clearly framed as opinion.

Step 4

Draft one section at a time

Draft section by section and keep your notes visible. Ask the AI to preserve your terminology and flag when it needs information you did not provide.

Example input

Draft section 2 using only these notes. Flag missing examples.

Expected output

A draft section with fewer unsupported jumps.

Common failure

The model adds generic examples that sound plausible.

Human check

Highlight every new example and decide whether to keep, source, or remove it.

Step 5

Edit for argument, not just grammar

Use the AI for a second-pass critique: missing logic, weak transitions, unsupported claims, and reader confusion. Do not let the final pass only polish wording.

Example input

Review this draft for argument gaps, unsupported claims, and unclear reader value.

Expected output

An editing checklist and targeted revision plan.

Common failure

The article becomes smoother but not stronger.

Human check

Ask whether each section moves the reader closer to the promised outcome.

Human review checklist

  • Check whether the AI output directly solves the original blog writing instead of drifting into a generic answer.
  • Verify all factual claims, dates, names, numbers, links, and quoted material against the original source or a trusted reference.
  • Remove unsupported claims, filler language, repetitive transitions, and confident statements that do not have evidence.
  • Compare the output with the intended reader, channel, and format before using it in public or sending it to another person.
  • Keep a short note of the prompt, tool, input material, manual edits, and final decision so the workflow can be repeated.

Mistakes to avoid

  • Starting the blog writing workflow with a vague prompt and no acceptance criteria.
  • Asking the model for a final answer before giving it source material, constraints, examples, or review rules.
  • Treating a fluent answer as correct without checking source coverage, missing assumptions, and edge cases.
  • Using the same prompt for research, writing, review, and final editing even though those are different jobs.
  • Skipping the human review step because the first output looks polished.

Related AI skills