Social Post
Take a social post from brief to ready-to-publish. The AI drives through Draft Variants and a Polish checkpoint.
the steps, as stored
- 01Brief
Establish the brief for this post. Do not draft yet.
Capture, in plain prose: - Platform — LinkedIn, X, or another, since format and length differ - Audience — who you are speaking to and what they care about - Core message — the single idea in one sentence - Proof or specific — a number, example, or detail that earns trust - Call to action — comment, click, follow, or none by design - Any link to include
If the core message is fuzzy, ask the operator before advancing — a vague message produces a forgettable post.
Save the full brief as a task note with task_notes_add. The next step — Draft Variants — reads this note.
- 02Draft Variants
Read the task notes with task_notes_list — the note from the Brief step contains platform, audience, message, proof, and CTA. Work from it.
Write three distinct variants of the post. What good looks like: - Each opens with a different hook angle (question, bold claim, story, stat) — not three rewrites of the same line - Each fits the platform's length and tone - Each carries the core message and the proof point - Each ends with the CTA from the brief
Label them Variant A, B, C so the operator can pick.
Save all three variants as a task note with task_notes_add. The Polish step reads this note and the operator's choice.
- 03Polishapproval gate
Read the task notes with task_notes_list — the note from the Draft Variants step contains Variant A, B, and C. Work from it.
Ask the operator which variant to run with. Polish the chosen one: tighten the hook, fix any awkward phrasing, confirm the link and CTA, check it reads well on the target platform.
Save the final polished post as a task note with task_notes_add. Then ask the operator to approve it 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 Draft Variants.
- 04Completecontext gate
The post is approved and ready to publish. Confirm the final post is saved as a task note, then close out the task.
use it for
- Announce a feature on LinkedIn with three hook options to choose from
- Turn a blog post into a short, on-brand social post
- Draft a post about a customer win and polish it before it goes out
without it, with it
| without | with social post |
|---|---|
| You stare at a blank post box and ship the first line that comes to mind | The AI drives a few distinct variants so you choose the strongest hook instead of settling |
| The post goes out the moment it is written, typo and all, with no second look | The AI pauses at a Polish checkpoint so you sign off before anything is published |
| You start a post on your phone, switch tasks, and lose the variants you liked | The AI saves the variants as a note, so you reopen the chat later and the options are still there |
| Nobody can tell which version went out or why that angle was picked over the others | Every step — Brief, Variants, Polish — is logged, so the record of what shipped and why is already there |