Agent Marching Orders — Master Index
Every agent’s mission, rules, and constraints in one place. If it’s not written here, the agent doesn’t know about it. Edit these to change agent behavior.
How This Works
Each agent has a Marching Orders file. When the agent runs, it should check its orders. When you want to change what an agent does, you change the orders here — not in code, not in a conversation, not in your head.
You edit Marching Orders in Obsidian
↓
Worker reads orders on startup / per job
↓
Agent follows updated rules
↓
No "Claude forgot" — rules live in files, not memory
Active Agents
Content Agents
- SeniorWire Blog Agent — Hyper-local county Medicare content, 6 cultural desks
- Content Planner Agent — Weekly Clone Pipeline for 5 clients
- SEO Hunter Agent Orders — Find long-tail keyword targets from CMS data
- SEO Healer Agent Orders — Write/optimize content from Hunter targets
Email Agents
- Reply Handler Agent — Classify replies, route to demo or blacklist
- Post-Demo Reply Agent — Send reply AFTER demo site is built
- PlusVibe Monitor Agent — Catch-all polling for missed webhooks
- Blacklist Checker Agent — Daily domain blacklist scan
Lead Agents
- Lead Prospecting Agent — GMaps → enrich → verify → score → export
- ICHRA Refresh Agent — Monthly county savings data update
Ops Agents
- Watchdog Agent — System health, worker restarts, disk/memory alerts
The Rule
If an agent is doing something wrong, the fix is HERE — not a conversation with Claude. Every directive must be:
- Written down (not just spoken)
- In the agent’s Marching Orders file
- Specific enough that any AI model could follow it
- Updated when the strategy changes