Boris Cherny (creator of Claude Code) mentioned in an interview that the entire plugins feature was built by Claude Code running over a weekend. An engineer gave Claude a spec & Asana board, and walked away. Claude broke it into tickets, spawned sub-agents and they executed independently. I watched that and thought “I need to do this.” Every time I tried, I came back to a mess. Blockers killed everything. One stuck ticket would halt the whole chain unless I babysat it through tasks one by one. When I tried running multiple agents in parallel, I’d watch two instances literally undo each other’s work in real-time. And the worst part? Half the time I was the blocker because the AI was waiting for me to provide an API key or make a design decision it couldn’t make alone. After a lot of frustration, I realised I needed a coordinator. So, I built an MCP that takes the product spec, breaks it into tickets, figures out which ones block each other and which can safely run in parallel, and crucially—surfaces inputs the AI will need from me before coding starts. After that, I walked away as the AI looped through building the tickets in parallel, testing, & code cleanup. It felt so good not having to babysit AI! The first thing I shipped with this workflow was a bot with vision that sees what you’re doing on your computer and proactively pings you helpful advice. In under an hour. I’ll share my MCP (Planvex) in the comments. Also happy to share advice if you’d prefer to build from scratch. P.S. If you’re a Claude Code guru, I also recommend Gitbutler to build faster without worrying about work trees, and the Ralphloop plugin so the AI can loop continuously. submitted by /u/Unfair-Marsupial-956
Originally posted by u/Unfair-Marsupial-956 on r/ClaudeCode