Blog Post AI workflow template: A blog post, brief to publish-ready.

The ConvOps Blog Post template makes your AI take a post from brief to publish-ready draft: pin the topic, reader, angle and call to action, build an outline, write the draft, edit it against the brief, then do a final read-through. You approve the outline before drafting and the post before publishing.

6 steps · 2 approvals · 1 loop back

Blog Post · example runyour AI client
  1. 01Brief
  2. 02Outlinewaits for approval
  3. 03Draft
  4. 04Edit
  5. 05Final Reviewwaits for approval
  6. 06Completeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Blog Post template do?

For marketers and founders who write with an AI and want the outline agreed before a full draft exists.

Blog Post is stored in ConvOps as six steps, and your AI client receives them one at a time. A Blog Post run holds at Outline and Final Review until an explicit approval is given.

  • Write a product-announcement post from a one-line brief to a publish-ready draft
  • Turn a rough idea into a structured article with a working title and clear sections
  • Edit a finished draft against the brief before it goes live
step by step

How does the Blog Post workflow run?

The 6 Blog Post steps in order, each with the instruction your AI receives there as Blog Post stores it.

Brief
Outlineapproval
Draft
Edit
Final Reviewapproval
Completeclosing note

A publish-ready post that went from a brief to an outline you approved, a draft, an edit against the brief and a final read-through.

  1. 01

    Brief

    the agent works

    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. 02

    Outline

    waits for your approval

    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.

    no rejection path · the run moves on only when approved

  3. 03

    Draft

    the agent works

    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. 04

    Edit

    the agent works

    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. 05

    Final Review

    waits for your approval

    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.

    rejected → back to Edit

  6. 06

    Complete

    closes with a note

    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.

reach for it when

  • A long-form piece needs its structure agreed before a full draft exists.
  • The post has to hold a stated angle and call to action.
  • Each stage should be saved so a draft can resume in a new session.

something else fits when

  • It is a short social post: Social Post gives you three hooks instead.
  • You are turning an existing piece into other formats: Content Repurpose.
  • The piece is a regulated disclosure with its own review route.
example · B2B marketing

A buying guide for procurement leads

The brief names the reader, the angle and the call to action. The marketing lead changes two sections at Outline, and approves the post once the final read-through has flagged a weak headline.

Outline and Final Review approvals

where approval is required

Where do you approve in Blog Post?

Blog Post holds at Outline and Final Review until an explicit approval is given, recorded with the account that gave it.

step 2

Outline

Fixing structure in an outline is cheap; fixing it in a full draft is not. You approve the title, hook and sections before drafting begins.

what you review

  • 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

no rejection path · approve to continue

step 5

Final Review

Publishing is the irreversible moment. The AI reads the post as the target reader would and surfaces anything off. Reject it and the run returns to Edit.

reject → back to Edit

gates the engine checks without you

  • Complete closes Blog Post only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Blog Post?

make it yours

How do you customize Blog Post?

Once installed, Blog Post is a workflow in your workspace. Ask your AI to change Blog Post in plain words; the edit lands on the one step that needs it.

ChatGPTexample

new chat

Add an SEO step after Edit that checks the title, headings and meta description.
workflow_step_add · Blog Post
Done. Blog Post in your workspace now has the change, and every new run follows it.

more example prompts

  • "Add an SEO step after Edit that checks the title, headings and meta description."
  • "In Brief, always load our brand voice guide."
  • "Add an approval to Draft so I read the first draft before the edit."
the difference

Blog Post: without a workflow vs with it

  • 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
  • The Blog Post process lives in a prompt, and each run follows it a little differently
  • 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
  • Your AI receives the 6 stored steps one at a time, and the run holds at Outline and Final Review until an explicit approval is given
questions

Blog Post template FAQ

What is the ConvOps Blog Post template?

The ConvOps Blog Post template makes your AI take a post from brief to publish-ready draft: pin the topic, reader, angle and call to action, build an outline, write the draft, edit it against the brief, then do a final read-through. You approve the outline before drafting and the post before publishing.

Can I close the chat mid-post and come back later?

Yes. In ConvOps, every step saves its output as a task note (the brief, outline, draft and edited version), and each next step reads the previous note with task_notes_list. A fresh session, or a different AI client, picks up exactly where the last one stopped. A draft over 10,000 characters is split across sequential notes or saved where you keep documents.

What does the Edit step check?

The ConvOps Edit step checks clarity (cut filler, fix any sentence that needs a second read), flow between sections so the hook still lands, the accuracy of every claim, alignment with the brief's angle, target reader and call to action, and whether the title is the strongest accurate option. The edited draft is saved as the current version for Final Review.

Does it publish the post?

No. The ConvOps Blog Post workflow ends with an approved, publish-ready draft saved as a task note, after the run holds at Final Review until an explicit approval is given. You or your AI client then publish it to your CMS with the tools you already use, and the approved version stays on the task as the record.

Why approve the outline before drafting?

Because structure is cheaper to change than prose. The ConvOps Outline step proposes a working title, a hook, H2 headings in order with a one-line summary each, the target reader and the closing call to action, all from the brief. The run holds there until an explicit approval is given, so no drafting starts on a structure you did not accept.