Blog Post

the steps, as stored

1. 01Brief

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

   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.

3. 03Draft

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

   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. 05Final Reviewapproval gate

   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.

6. 06Completecontext gate

   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.

use it for

• 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

without it, with it

say this in your client