When should you use it?
- You wear every hat and things like tax deadlines slip
- Your work crosses domains, such as marketing claims with legal risk
- You are happy keeping agent instructions as files in a repo
Not for: Replacing a qualified accountant or lawyer for filings; Letting agents post publicly with no human check
What do you need, and what do you get?
You need
- A file of concrete rules for each role
- A shared memory store
- Tool access such as error tracking and a task board
You get
- A daily prioritized plan from the ops agent
- Review verdicts when one agent's work touches another's area
- A growing log of lessons the meta-agent turns into updates
How does it work, step by step?
- Write role files with specificsEncode real rules, for example local VAT deadlines, voice guidelines or banned marketing words, not generic helpfulness.
- Share one memoryStore decisions, deadlines and lessons where every role can read them, with pruning for stale standups.
- Define review triggersMake claims go to the legal role and pricing go to the tax role, and cap how deep calls can chain.
- Start the day with a standupHave the ops role check errors, overdue tasks and periodic duties, then hand out work.
- Log lessons after hard tasksLet a meta-agent read the lessons monthly and propose edits to the other roles.
The prompt
Our own prompt, inspired by João Pedro Silva Setas and written to work in Microsoft Copilot and Custom agent. Values in lime are placeholders.
You are the [role] for my one-person company. Your rules: [domain specifics, e.g. local tax deadlines, banned marketing words]. Read the shared memory before starting. If your work makes a claim, a price or an infrastructure change, request a review from [legal / tax / cost role] and include the call chain; never exceed three hops. Record any decision and any lesson learned in memory. Do not publish, file or send anything; hand me a draft and the reviewers' verdicts.
Inspired by João Pedro Silva Setas: I Run a Solo Company with AI Agent Departments. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Simultaneous writes damaged the shared memory file until locking was added.
- Agents still invent things; the cross-review exists precisely because of that.
Our take
The org chart matters less than the review triggers he wired in. Most solo founders end up with one assistant doing everything and nobody checking, which is how marketing claims go live without a second look. Routing a product claim to a compliance-minded role, or an infrastructure idea to a cost-minded one, is a cheap way to catch errors before they are public. Sharing a persistent memory graph lets the roles build on each other across days, which is also where the author reports pain: corrupted shared memory and hallucinations that the review layer then has to catch. Keep anything that publishes, files paperwork or spends money behind your own approval, no matter how firmly the agents agree among themselves. Write each role file with concrete do's and don'ts rather than job titles alone, and give the improver a narrow brief so it does not rewrite everything weekly. Log lessons after hard tasks so the next run starts wiser. Review the shared memory monthly and prune entries that are wrong or outdated.
Where the time goes back: Routine checks that a solo founder skips, like vetting a claim or a cost impact, happen automatically before the work ships.
FAQ
Does this replace professional advice?
How do you stop agents calling each other forever?
Source and credit
Inspired by João Pedro Silva Setas. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I Run a Solo Company with AI Agent Departments
- Creator
- João Pedro Silva Setas
- Published on
- DEV Community (dev.to)
- Original date
- Mar 3, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Microsoft Copilot
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
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.