Blog Post

Take a blog post from brief to published draft. The AI drives through Outline, Draft, Edit, and a final read-through.

Marketing 6 steps 2 checkpoints Human approval Self-correcting
Use this workflow

Free to start · runs with your own AI

Workflow steps

Runs inside your AI conversation · the orchestrator drives

"Write a blog post about our new pricing page"

you — in any AI chat

  1. 1

    Brief

    Establish the brief for this post. Do not start writing yet.

    Capture, in plain prose:

    • Topic — what the post is about, in one sentence
    • Target reader — who this is for and what they already know
    • Angle — the specific take or insight, not a generic overview
    • Goal — what the reader should think, feel, or do after reading
    • Primary call to action — the one next step you want

    If any of these is missing or vague, ask the operator before
    advancing. A weak brief produces a weak post.

    Before advancing, save the full brief as a task note with
    task_notes_add. The next step — Outline — reads this note as its
    named input.

  2. 2

    Outline

    Read the task notes with task_notes_list — the note from the Brief
    step contains topic, reader, angle, goal, and CTA. Work from it.

    Build the outline. What good looks like:

    • Working title — specific, not a placeholder
    • Hook — the opening line or idea that earns the next sentence
    • H2 section headings in order, each with a one-line summary of
      what that section argues or delivers
    • Target reader restated so the structure stays aimed at them
    • Closing CTA matching the brief

    Keep the outline tight — a reader should grasp the whole arc from
    the headings alone.

    Save the full outline as a task note with task_notes_add. Then ask
    the operator to approve the outline before any drafting begins.
    This is a checkpoint — the AI cannot advance until you approve.

    The AI pauses here and waits for a human to approve before the conversation continues.
  3. 3

    Draft

    Read the task notes with task_notes_list — the note from the Outline
    step contains the approved structure. Work from it.

    Write the full first draft following the approved outline section by
    section. Hold to the angle and the target reader from the brief. Use
    concrete examples over abstractions. Write the real hook, not a
    placeholder. Do not pad to hit a length — every paragraph earns its
    place.

    Before advancing, save the full draft as a task note with
    task_notes_add so the Edit step — or a fresh session — picks up
    exactly here. If the draft exceeds 10,000 characters, split it across
    sequential notes or save it where the operator keeps documents and
    record that location in the note.

  4. 4

    Edit

    Read the task notes with task_notes_list — the note from the Draft
    step contains the full first draft, and the Brief note holds the goal
    and CTA to check against. Work from them.

    Edit the draft for:

    • Clarity — cut filler, fix any sentence that needs a second read
    • Flow — each section leads into the next; the hook still lands
    • Accuracy — every claim is correct and specific
    • Brief alignment — the angle, target reader, and CTA all hold
    • Title — confirm it is the strongest accurate option

    Save the full edited draft as a task note with task_notes_add,
    replacing the working draft as the current version. The Final Review
    step reads this note.

  5. 5

    Final Review

    Read the task notes with task_notes_list — the note from the Edit
    step contains the current version. Work from it.

    Do a final read-through as the target reader would. Confirm the title,
    hook, sections, and CTA all deliver on the brief and that nothing is
    broken or unfinished. Surface anything still off.

    Ask the operator to approve the post for publishing. This is a
    checkpoint — publishing is the irreversible moment, so the AI cannot
    advance until you approve. If you reject, the workflow returns to Edit.

    The AI pauses here and waits for a human to approve before the conversation continues.
    If rejected → returns to edit
  6. 6

    Complete

    The post is approved and ready to publish. Confirm the final approved
    draft is saved as a task note so the published version stays on the
    record, then close out the task.

  7. Workflow complete — outcome delivered, every step on record.

Why this workflow?

Without a workflow

  • A post gets drafted with no outline, wanders off topic, and never matches the brief you started from
  • You close the chat halfway through the draft and lose the whole thread of where the piece was going
  • Nobody can tell which draft is current or what changed between the outline and the published version

With ConvOps

  • The AI drives through an Outline you approve at a checkpoint before a single paragraph gets written
  • The AI saves each stage as a note, so you reopen the chat next week and pick up exactly where the draft left off
  • Every step — Brief, Outline, Draft, Edit, Final Review — is logged, so the full history of the post is already there

Related workflows

Ready to automate?

Stop re-explaining your process. Pick a template, start a task, and let the AI drive the work through your workflow.