Prepping Your Repo for Autonomous Programming

Episode Summary Dave and Dan break down the upfront infrastructure work required before a single repo is ready for autonomous programming. They walk through the full prep checklist — monorepo structure, lazy-loaded docs, 90% test coverage with end-to-end tests, a dev environment that actually matches prod, canary deploys, and observability — and explain why each one is non-negotiable when you're shipping code without a human in the loop. Key Topics Why monorepos win — a root-level CLAUDE.md that knows how all your services interact, plus per-service docs underneath Progressive disclosure for context — keep CLAUDE.md under 200 lines and lazy-load topical docs (data model, GitHub Actions, Terraform, API endpoints) A daily docs cron — agents that update your docs every morning so context never goes stale Agent validation = tests + lints — 90% coverage as a hard gate, unit + end-to-end, all green before merge Shipwright crons in practice — development, review, docs, golden principles, cruft cleanup; one of them found and fixed an unauthorized Stripe webhook overnight Dev parity, canary deploys, and observability — the safety stack that makes shipping without a human safe (yes, just pay for Datadog) Notable Quotes "You can't just turn it on and expect magic to happen. There's a bunch of upfront work — we call it infrastructure — around your repository." "You're shipping code without a human involved. So you gotta put in as many safety things as possible. You gotta burn those extra calories to make sure dev is the same as prod." "I am an open source guy, but if it was up to me — just bite the bullet. Pay for Datadog and use APM." "By the way, these are things that would benefit any organization even if you aren't autonomous. Every org should be doing this anyway." About The Velocity Lab Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field. Subscribe: RSS