While building OtterForm, I had one of those moments where AI felt like a superpower and a limitation at the same time. At the beginning it is incredible with features that moved fast, boilerplate disappeared, and it genuinely felt like we had added another developer to the team. But as OtterForm grew into a real product with integrations, edge cases, and long-term architectural decisions, the cracks started to show. AI can write code, but I was still the one holding the system together, acting as the PM, architect, QA, and integration layer all at once.
Every development cycle started to look the same: explain context, get code, restructure it, align it with the rest of the system, and fill the gaps the AI didn’t see. The issue wasn’t intelligence, the models are very strong: it was workflow. So instead of trying to “prompt better” I built something that I actually needed: a way for AI to work like an AGILE development crew, not a chat assistant.
That system became CODEMUS. You don’t talk to “AI” directly; you work through a PM role that turns ideas into structured requirements, tasks, and coordinated work across dev-style roles. Less prompt juggling, less chaos, more process. It’s the internal system that helped us keep OtterForm sane as complexity grew, and now we’re turning it into a software running on a Mac.
It requires Claude Code (PRO or MAX). Have a look if it might be of any interest.