The Flywheel Planning Playbook¶
Definitive guide to building software with AI agent swarms.
Get Started | Prompt Catalog | Zero to Hero
Most people using AI agents are doing it wrong. Not slightly wrong. Catastrophically wrong. They open Claude, describe what they want, accept whatever comes back, and move on. Then they wonder why the code is brittle, the architecture is incoherent, and they spent three days debugging something an agent wrote in four minutes.
Planning tokens are cheap. Code tokens are expensive. Debugging tokens are ruinous.
| Activity | How most people work | How this works |
|---|---|---|
| Planning | ~10% | ~85% |
| Implementation | ~70% | ~10% |
| Review/Fix | ~20% | ~5% |
That's not a typo. Eighty-five percent planning. A 6-hour planning session prevents 60 hours of agent chaos. A bad plan wastes multi-agent hours across parallel workers. A good plan pays for itself before the first line of code.
There is a deeper flywheel most people miss: each project you build becomes a library for the next project. The tools compound. FrankenTUI feeds FrankenSQLite feeds FrankenTerm feeds Agent Mail Rust. The February 2026 Rust Agent Mail port stacks 10 self-built libraries. That compounding -- each project consuming previous projects and becoming infrastructure for the next -- is the actual flywheel. The planning methodology is just the engine that makes each rotation clean enough to build on.
What's in this guide¶
| Section | What you get |
|---|---|
| 12 Principles | The ideas behind the workflow |
| 9 Phases | Sequential steps from prerequisites to performance |
| 47 Prompts | Verbatim, copy-paste, organized by category |
| Dispatch Table | "When in situation X, use prompt Y" |
| Toolchain | 23 tools that make the flywheel turn |
| Anti-Patterns | 14 ways to destroy your project |
| Doctrine | 14 non-negotiable rules |
| Zero to Hero | The complete guide: strategy, operations, and reference in one place |
Attribution¶
Based on Jeffrey Emanuel's agentic coding methodology. Incorporates the Flywheel Planning Playbook by @voidserf. Extended with forensic analysis of 5 repos, 69 sessions, and 8,914 tweets.