I've all but given up on these types of approaches. Models will often just ignore your process instructions at the most inopportune moments. For work, I've resorted to mostly just using single agents for smallish pieces of work that I orchestrate myself. I treat it as a tool, with me being the craftsman.
Everyone is pushing Agent Fleets and Swarms, and I'm sure that there are many success stories, but from our internal experiments many devs don't see any speed advantage for complex work. Here's what one of them told us recently: "The speed advantage is offset by the manual refactoring work. The code is 'correct', but it's just not what any of us would have written".
Now one could argue that you could just ignore the code if it's working (that is in fact what Ex Co instructed us to do) and just keep running these fleets if the end result "works", but I'm not fully convinced this will end well in the long term.
Then again, I'm stuck with decades of legacy code and systems that noone understands that were introduced by humans...
Everyone is pushing Agent Fleets and Swarms, and I'm sure that there are many success stories, but from our internal experiments many devs don't see any speed advantage for complex work. Here's what one of them told us recently: "The speed advantage is offset by the manual refactoring work. The code is 'correct', but it's just not what any of us would have written".
Now one could argue that you could just ignore the code if it's working (that is in fact what Ex Co instructed us to do) and just keep running these fleets if the end result "works", but I'm not fully convinced this will end well in the long term.
Then again, I'm stuck with decades of legacy code and systems that noone understands that were introduced by humans...