Show and tell: the architect/builder method. I use it in real life at my day job, and now every time I build with AI. At work I architect solutions for developers. The loop goes like this. They go off and come back with a plan, we talk it through, I add the things they hadn’t thought of, and we land on a better plan. Then they build and I review. With AI it’s the same loop, just with two separate chats. The architect chat plans with me. It asks the questions I’d forget to ask, never writes any code, and the plan goes into a file. Then a fresh builder chat reads only that file, tells me how it would build it, and stops so I can look before anything gets made. After that it builds one piece, tests it, and reports back. Why I like it, at work and with AI: it tends to find problems before they’re built. The plan gets talked through before anyone writes a line, so you catch the gaps while they’re still cheap to fix. One thing has to come first, though, and that’s getting organized. The plan and the decisions live in files, so you can close a long chat without losing anything and the next one picks up where the last one stopped. That matters because AI gets worse the longer a chat runs. If you’re in here you’ve got a head start, since the knowledge base setup Miles teaches is the same idea. It’s what I did first too, before clients or business ideas, and I’ve had clients come to me just wanting that part. I walk through the whole thing here: https://youtu.be/rRRsZmKoAho Anyone else split planning and building like this? Or do you plan in the same chat you build in?