Planning bots — the category nobody talks about

Most folks use one bot for everything. That's why their AI projects spin.

The walkthrough

1. Most folks use one bot for everything. That's why their AI projects spin.
2. Plan, code, deploy, debug — all the same bot.
3. Output: 200 lines that miss your intent. Sound familiar?
4. The fix is splitting the job in two.
5. One bot plans. Reads your folder. Writes the steps.
6. In practice: Claude Code Plan Mode. That's a planning bot.
7. Different bot executes. Picks one step. Does it. Reports back.
8. Execution bot reads the plan. It doesn't replan. It builds.
9. Loop: plan a step. Execute. Review. Plan the next step.
10. Same task. Split-bot version is ~60% fewer mistakes in my own runs.
11. Each bot has one focused job. Smaller context. Cheaper tokens.
12. Plan with the smart model. Execute with the cheap one.
13. Same pattern as a contractor and crew. Foreman plans. Crew builds.
14. Big jobs go from $5 a run to $0.50. Same outcome. — TODO: confirm exact numbers from my logs
15. Use it for: refactors. Multi-step builds. Audits. Migrations.
16. Don't bother for: one-line edits. Copy tweaks. Tiny jobs.
17. Both bots read the same CLAUDE.md. Shared context. Different roles.
18. Split the planner from the builder. That's the trick.
19. localmodeldojo.com — Founder pricing $24/mo for life · code LAUNCH30 · 30 days only

— Jake Morris · Oklahoma veteran · localmodeldojo.com