I gave a folder a content team. The organization chart? A simple .md file. I cre
By John Aspinall ✱ · October 5, 2026 · Curated by George's Blog
I gave a folder a content team.
The organization chart?
A simple .md file.
I created a Codex project called “LinkedIn Test” and added an AGENTS.md file that defined how the work should get done.
Here’s the setup, and how you can repeat it.
1/ Define the jobs
I gave the project five roles:
→ Researcher: gather sources and verify claims
→ Copywriter: turn the research into a post
→ Creative Designer: turn the findings into a visual
→ Proof Reader: review the package
→ Orchestrator: coordinate the handoffs
Each role had defined inputs, responsibilities, output files and completion criteria.
“Be a marketing expert” leaves a lot open.
“Use this research, write this file, flag unsupported claims and return it for review” gives the agent an actual job.
2/ Put the handoff rules in AGENTS.md
AGENTS.md is a project instruction file Codex reads.
Mine explains how to call each role individually or run the broader workflow. It tells the main agent when to delegate, what context to pass, and where the specialist should save its output.
It also says agents can work in parallel when their inputs are stable and they’re writing separate files.
No two writers fighting over the same document. Imagine that.
3/ Start with a real request
I typed:
“Researcher, do a deep dive on what was trending this week on LinkedIn in AI tools. Then hand it off to Copywriter to write a first draft.”
The researcher produced a source-backed packet and handed it to the copywriter.
One important detail: access to public posts doesn’t prove what’s trending across all of LinkedIn. The research disclosed that limitation.
4/ Add another specialist
While the workflow was running, I asked the Creative Designer to make an infographic from the research.
Research came first. Writing and design could then overlap because they had a stable source to work from.
The actual run used three specialist subagents: Researcher, Copywriter and Creative Designer. The main agent coordinated them.
5/ Keep the work together
The project ended up with:
→ A brief
→ Research and source notes
→ A first-draft post
→ Design notes and an infographic PNG
→ A status record
The five-role workflow included proofreading and publishing stages, but this test stopped at draft production. No separate Proof Reader had cleared it. Nothing was published.
That distinction matters.
To try this, open a local folder in Codex and ask it to create an AGENTS.md defining your roles, inputs, outputs, handoffs and review gates. Then give one role a specific task.
Saving the file doesn’t launch employees who work forever. The task starts the work, using the delegation tools available.
For Amazon brands and operators, this can become a repeatable path from product facts to creative briefs, listing copy and reviewable content.
The useful part is deciding who does what, what they hand over, and how you know it’s ready.
Your next prompt shouldn’t have to explain the entire company again.