1
0 Comments

the doc I write before every AI agent now

Month 2 of running 10+ AI agents for PM work, my Claude bill was 3x what I expected. No clear reason - every agent was "working."

Turned out I had no budget constraints in any of them. Each one had free rein on tokens and scope. Made sense at the time.

Now every agent gets a constraints doc before I deploy: max tokens per run, and which decisions stay with me. Writing "what this agent can't do" takes 3-4 iterations. It's genuinely harder than "what it does."

Two things improved: bill down ~40%, and I stopped getting silent completions - agents succeeding at tasks that weren't quite their job. Those are the worst to catch.

Next step is making the constraints doc the first required artifact in my deployment flow, not an afterthought.

Do you write anything like this before you hand work to an agent? Curious if there's a cleaner format than what I'm using.

posted to Icon for group AI Tools
AI Tools
on May 29, 2026
Trending on Indie Hackers
I built a WhatsApp AI bot for doctors in Peru — launched 3 weeks ago, 0 paying customers, and stuck waiting for Meta to approve my app User Avatar 52 comments Fixing broken scrapers instead of working on my actual product. So I made it my problem. User Avatar 44 comments I built an open-source PII masking layer for LLM APIs — early traction, looking for design partners User Avatar 33 comments How to see revenue problems before they get worse User Avatar 29 comments From broke and burned out as a PM, to launching my SaaS and optimizing my health User Avatar 27 comments I kept starting projects and dropping them. So I built a system that wouldn’t let me User Avatar 23 comments