When should you use it?
- You already use Claude Code and handle marketing yourself
- Your marketing work repeats on a weekly rhythm
- You prefer files you can edit over a new platform
Not for: Publishing without anyone reading posts first, until rules are proven; Teams that can't keep API keys out of agent logs
What do you need, and what do you get?
You need
- Claude Code with the agent teams feature
- One markdown file per role with scope, tools and hard rules
- A weekly plan in time slots and a shared rules folder
- Scripts or MCP servers for your CMS and social accounts
You get
- Blog drafts, social replies and posts produced on schedule
- A CSV log of every action
- A weekly insights file other agents read before working
How does it work, step by step?
- Write roles as job descriptionsGive each agent file a title, scope, documents to read, tools, step order, hard rules and error handling.
- Write the team charterPut structure, delegation and security rules in CLAUDE.md, and cross-agent policies in a rules folder.
- Plan in time slotsMap each day into slots that spell out each agent's job; agents should not work ahead.
- Log and reviewHave the social agent record each action in a CSV and the reviewer turn it into an insights file.
- Fix rules with examplesWhen an agent misbehaves, add a concrete example to its rules rather than a general principle.
The prompt
Our own prompt, inspired by u/Practical_Dig6095 on r/AskGTM and written to work in Claude Code, Claude and ChatGPT. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Write a Claude Code agent file for the role {role} on my marketing team. Include frontmatter (name, description that tells the lead agent when to call this role, model). Then: required reading ({docs}), tools and scripts allowed ({tools}), the step-by-step workflow for {main_task}, hard rules written as concrete do/don't examples, what to log and where, and what to do when blocked. Keep it under 80 lines.
Inspired by u/Practical_Dig6095 on r/AskGTM: Automated my Marketing Operations with Claude Code.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The author's social agent double-posted in week one because the rule was too vague; write rules with examples.
- The content writer once created empty CMS drafts; enforce the order body, image, draft, publish.
Our take
Thinking of each agent as a new hire with a job description is the most transferable idea here. A role file that lists what to read first, which tools to use, the exact sequence and the hard rules is something you can review and improve, unlike a long chat history. The weekly plan in time slots is the other strong choice: it keeps agents from improvising work and makes the system's behavior predictable. His two failure stories are worth more than the architecture diagram. Duplicate Reddit comments and empty CMS drafts both came from rules that sounded clear to a person but weren't specific enough for an agent, and the fix was concrete examples. If you copy this, keep a human approving anything public for the first weeks, especially community replies on Reddit and Hacker News where tone mistakes are costly. Start with two roles, not five, and add the reviewer early, because the feedback loop is what makes the setup improve rather than just repeat.
Where the time goes back: Recurring marketing tasks run from a written plan, and fixes to one rule file apply to every later session.
FAQ
Did he write code?
How do agents share what they learn?
Source and credit
Inspired by u/Practical_Dig6095 on r/AskGTM. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Automated my Marketing Operations with Claude Code.
- Creator
- u/Practical_Dig6095 on r/AskGTM
- Published on
- Original date
- May 25, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.