You do not need a writer, a researcher, an editor, a strategist, and a scheduler.
You need five markdown files and a folder.
Save this. You will read it twice.
Most people use Claude as one tool.
They open a chat. They type a prompt. They get an article. They copy it somewhere. They open another chat.
That is the assembly line model. You are the conveyor belt.
The smarter model is a pipeline. Each agent has one job. Each job feeds the next. Output of Agent 1 becomes input of Agent 2. By the time the content reaches Agent 5, it has been researched, written, edited, formatted, and scheduled.
You touched it once at the start. You touch it once at the end.
This is how solo creators now out-produce editorial teams of twelve.
Why Chaining Beats Prompting
A single Claude session is a generalist.
A chained pipeline is a specialist team.
The difference is not capability. It is context contamination.
When you ask one Claude session to research, write, edit, and format in a single thread, the model is context-switching every few messages. The researcher persona blends into the writer persona. The editor is reluctant to cut what the writer just produced. The strategist defers to whatever the session already committed to.
When each agent runs in its own context window with its own instructions, there is no contamination. The editor has never seen the writer's draft emotionally. The strategist does not know how long the research took. Each agent does exactly one job and does it without attachment to what came before.
That is why chained pipelines produce better content than long single-session prompts.
How the Pipeline Works
Five agents. One input. One finished piece.
You give the Strategist a topic and an audience.
The Strategist returns an angle, a hook, and a content brief.
The Researcher takes the brief and returns primary sources, key facts, and three contrarian data points.
The Writer takes the brief plus research and produces the full draft.
The Editor cuts 30%, sharpens the opening, rewrites the close.
The Publisher formats for the target platform, adds SEO structure if needed, and outputs the final file.
Total human input: two paragraphs and a platform target.
Total human output: finished, platform-ready content.
The 5 Agents (Complete Files)
01. The Strategist
What it does: Takes a raw topic and audience. Returns the specific angle that will perform, the hook, the content brief, and what not to write.
Fire it when: You have an idea but you are not sure if it is the right angle or if it will stand out. Start here. Always.
02. The Researcher
What it does: Takes the content brief from the Strategist. Returns primary source facts, statistics, and three contrarian data points that most writers miss.
Fire it when: The Strategist has returned a brief and you are ready to build the argument. Do not let the Writer start without the research. Every weak article is a research failure, not a writing failure.
03. The Writer
What it does: Takes the content brief and research pack. Writes the full draft to the exact structure, length, and platform spec. Does not edit. Does not second-guess the brief.
Fire it when: The Strategist has the angle, the Researcher has the facts, and it is time to actually write. The Writer's job is execution, not invention.
04. The Editor
What it does: Takes the Writer's draft. Cuts 30%. Sharpens the hook. Rewrites the close so the last line is the one people share. Returns the edited draft plus a change log.
Fire it when: The Writer has returned a draft and you are too close to it to see what is weak. The Editor has never seen the draft before. It has no attachment to any of it. That is the point.
05. The Publisher
What it does: Takes the edited draft. Formats it for the target platform. Adds SEO structure if the platform needs it. Outputs the final file, ready to publish.
Fire it when: The edited draft is final and you need it in the right shape for the platform. The Publisher does not judge the content. It ships it.
How to Run the Pipeline
Three ways. Pick yours.
Claude Code: Create .claude/agents/ in your project root. Save each agent as its own .md file. Run them in sequence: /agents content-strategist, pass the output to /agents content-researcher, and so on. Claude finds the agents automatically.
Claude.ai: Settings → Sub-Agents → Add. Paste each file. Call them by name in your conversation. Chain the outputs manually by copying each agent's output into the next agent's input.
Claude Desktop: Same as Claude.ai. Settings → Sub-Agents → Add. Five agents in the sidebar. Run in order.
The Handoff Protocol
This is the part nobody talks about.
Running five agents is not enough. You need clean handoffs.
Use this template every time you pass output from one agent to the next:
This single template eliminates 90% of pipeline drift. The receiving agent knows exactly where it is in the sequence and does not try to redo work that is already done.
A Real Run: From Topic to Published Thread
Input to Strategist:Topic — "Claude sub-agent pipelines for creators" Audience — "Solo founders and content creators" Platform — "Twitter/X thread"
Strategist returns:Angle — "Most people use Claude as one assistant. The ones outproducing teams use it as five." Hook — "You do not need a writer, a researcher, an editor, a strategist, and a scheduler. You need five markdown files and a folder." Avoid — "Another 'Claude is amazing' thread with no specifics."
Researcher returns:3 key facts, 5 sources, contrarian data: "Multi-agent setups are 3-4x slower to set up, but produce 6-8x the content volume per month."
Writer returns:Full 1,200-word draft in 4 minutes.
Editor returns:Same draft at 840 words. Opening rewritten. Last line now quotable.
Publisher returns:9-tweet thread. Tweet 1 is the hook. Tweet 9 is the CTA. Each tweet is under 280 characters. Ready to paste.
Total time from input to publish-ready: 18 minutes. Total words written by the human: one paragraph.
The Uncomfortable Truth
Most people will save this and go back to typing prompts into one chat window.
A few will install all five agents and chain one piece of content end to end this week.
A smaller group will run the pipeline every day for 30 days and realize they have been doing the equivalent of driving to a destination on foot.
The gap is not intelligence. It is not access. It is whether you opened the folder and pasted the files.
Every piece of content you produce by typing into a single session is a piece of content your competitor's pipeline already shipped two hours ago.
Five agents. One folder. One pipeline.
Open the folder.
TL;DR
5 sub-agents. One content pipeline. A creative team in a folder.
Strategist — finds the angle before anyone writes a word. Researcher — builds the argument on real sources. Writer — executes the brief, no second-guessing. Editor — cuts 30%, sharpens everything. Publisher — formats for the platform, ships.
The team is the file. Open the folder.
