Create LinkedIn visuals

We are working in ONE conversation. Every turn from here builds on the last. Do not restart, do not ask me to re-paste anything, and do not ask me to confirm the brief - it is below.

The brief

I want a publish-ready content calendar with all posts written.

There is a standing automation that normally produces this. It is called LinkedIn Visual Automation, and the video that demonstrates it is titled "OpenAI's Image API Just Changed the Game (save 10+ hours/week, n8n tutorial)". Here is what that pipeline actually does:

In this workflow, Nate Herk demonstrates a comprehensive AI automation system for marketing on LinkedIn. The process begins with a form submission gathering email, post topic, and target audience, and then uses two AI agents: one to generate a research-backed post and another to convert it into a dynamic image prompt. The system integrates the OpenAI Image Generation API, Tavi for web search, and HTTP request tools for API calls along with binary conversion. A free template is available via his Skool community.

The original pipeline is built in n8n and wires together: OpenAI, n8n, LinkedIn.

What is different about this session

That automation is a permanent pipe. I do not want the pipe. I want the output, once, produced by you working through this conversation with me over the next few turns. Do not produce an n8n JSON export, a node graph, or a workflow diagram. Produce the thing the pipe was built to produce.

Your job right now

1. Read the brief and restate the deliverable in one sentence, in your own words, so we agree on what "done" means.
2. Write a numbered execution plan - the actual production steps, in order, that you will carry out across this conversation. Be concrete: each step names an artefact it will produce.
3. List the inputs I must give you for the plan to be executable. For each one, show the exact shape you want it in, with a fill-in-the-blank template I can type over. Assume I have none of this ready.
4. Flag anything in the brief that is ambiguous or that you will have to assume. Make an explicit, defensible assumption rather than asking a vague question.
5. State the final output format you will produce in the last turn (file layout, sections, length).

Constraints for everything you produce in this conversation:
• Concrete and finished. No placeholders left where a real value belongs, no "insert your X here".
• If you cannot verify a fact, say so inline rather than inventing it.
• Every claim that rests on an external fact gets a source.
• Optimise for something I can act on this week, not for a textbook answer.

Before you continue: The assistant should restate the deliverable and give you a numbered plan plus the inputs it needs. Answer its questions before continuing.

Continue from Turn 1. Do not re-plan from scratch.

Take the numbered plan you produced and turn it into a locked execution checklist:

1. Restate it as a checklist where every line is a specific artefact with a one-line definition of "finished". For example: #3 - Hook table: 10 hooks, each <= 8 words, each paired with the segment it comes from.
2. Tell me, in priority order, which inputs I must supply right now to unblock the most work. Give me a single copy-paste block with the fill-in-the-blank fields already laid out. If an input genuinely cannot be typed (a file, a link list, an API response), tell me exactly what to paste and what shape it should be.
3. Where you made an assumption in Turn 1, state it again in one line and tell me what it would cost if it is wrong. Mark each assumption as HIGH or LOW impact.
4. Tell me the order you will work in and exactly which turn each checklist item lands in, so I know what I am waiting for at each step.

Then stop and wait for my input. Do not start producing deliverables yet - I need to see the checklist first.

Before you continue: The assistant produces this stage. Read it, answer anything it asks, then paste the next turn in the same chat.

Continue in this same conversation. Everything below builds on Turns 1 to 2; do not restart or re-brief yourself.

Get the audience straight before writing a word.

1. Define the audience precisely - who they are, what they already believe, what they are sceptical of, and what they are trying to do. Not demographics - psychology.
2. State the positioning in one sentence: what you are known for that a competitor is not. If that sentence is hard to write, that is the finding.
3. List the content pillars - three to five themes you will own, each with why it is defensible.
4. Identify the anti-pillars: what you will never post, and why that protects the brand.
5. State the single point of view that will make the content feel like a person wrote it.

Output a positioning brief. It will be referenced in every draft, so it must be sharp.

Before you continue: The assistant produces this stage. Read it, answer anything it asks, then paste the next turn in the same chat.

Continue in this same conversation. Everything below builds on Turns 1 to 3; do not restart or re-brief yourself.

Build the calendar.

1. Produce a 30-day content calendar: date, pillar, format, platform, working title, and the hook in one line.
2. Write the hook for every item - the first line, under 12 words, written to earn the second line.
3. Flag the items that are evergreen versus time-sensitive.
4. Mark the two posts that you think will perform best, and say why in one line each.
5. Tell me which four posts I should write first if I only have time for four.

Output as a table. Hooks must be genuinely varied in mechanism - not 30 variations on one.

Before you continue: The assistant produces this stage. Read it, answer anything it asks, then paste the next turn in the same chat.

Continue in this same conversation. Everything below builds on Turns 1 to 4; do not restart or re-brief yourself.

Write the posts.

1. Write the first five posts in full, finished and ready to paste. Body, and the opening line that survives the fold.
2. For each, note the format detail: length, line breaks, whether it needs an image or a video, and what that should be.
3. Write three engagement prompts that invite a real reply rather than a like - each attached to a specific post.
4. For each of the five, give the one-line note on what the post is doing - teaching, provoking, demonstrating, or connecting.
5. Show me one post written in a deliberately different voice, so I can see the range.

Output the five posts in full. No summaries, no "expand on this".

Before you continue: The assistant produces this stage. Read it, answer anything it asks, then paste the next turn in the same chat.

Continue in this same conversation. Everything below builds on Turns 1 to 5; do not restart or re-brief yourself.

Make one piece of work go further.

1. Build a repurposing matrix: take the best post and list every format it becomes - thread, carousel, short video script, email, quote card. With the adapted opening line for each.
2. Write the thread version of the strongest point, with each post standing alone and the sequence earning the next.
3. Write the native adaptation for each platform - what changes when the same idea moves to another one. Say what changes, do not just restate.
4. Give the posting timing recommendation and the reason.
5. Give me the one-week test: what to measure, and what result would mean change the plan.

Output so I can execute without re-deciding anything.

Before you continue: The assistant produces this stage. Read it, answer anything it asks, then paste the next turn in the same chat.

Everything is produced. This turn is about making it one coherent thing rather than a pile of parts.

1. List every artefact produced so far in this conversation, by the name we agreed in the checklist. Flag anything from the checklist that is missing or thin.
2. Cross-check the parts against each other and report the inconsistencies you find. Be specific: which artefact says one thing and which says another. Fix them, and show the fix.
3. Rewrite the pieces that depend on each other so they use one consistent vocabulary, one consistent naming scheme, and one consistent tone. Show the corrected versions of anything you changed.
4. Identify the three weakest parts of the work and tell me honestly what would improve them. If you think something should be cut rather than polished, say so.
5. Produce a short READ ME FIRST section for the final deliverable: what this is, who it is for, how to use it, and what to do first.

Keep the README under 300 words.

Before you continue: The assistant produces this stage. Read it, answer anything it asks, then paste the next turn in the same chat.

Now assemble the finished a publish-ready content calendar with all posts written.

1. Produce the complete deliverable in the format you committed to in Turn 1. Use every artefact from this conversation - do not start over, and do not leave anything as a note to self. This is the version I keep.
2. Run a self-check before you send it, and show the check as a short table at the end:
   • Is every checklist item from Turn 2 actually covered? List any that are not.
   • Does anything still contain a placeholder, a TODO, or an unverified claim?
   • Is the thing internally consistent - numbers, names, dates, cross-references?
   • If a real person acted on this on Monday morning, what would they trip over? Fix it.
3. Give me a NEXT 3 ACTIONS list: the three concrete things to do next, each with an owner and a timeframe. Not a wishlist - three things I can start.
4. If any part of this deliverable should be regenerated weekly or monthly, say which part and give me the single prompt that would do it, so I can reuse it.

Output the deliverable first, then the self-check table, then NEXT 3 ACTIONS.

Before you continue: The assistant produces this stage. Read it, answer anything it asks, then paste the next turn in the same chat.