So I was tokenmaxxing yesterday on Fable and I guess the biggest change I noticed from using Opus as the main driver is that Fable doesn't want me to do small implementations, when we planned a new feature it pulled in a lot more and made the feature bigger and better during the planning.
When it was done with the planning of a feature Opus usually created separate github issues and put in memory which ones are related, Fable on the other hand went ahead and created Epics first and split all things it needed to implement in a list of issues which it then used to create all of these with thorough instructions so that whatever model picks it up, they can implement it without any bigger issues.
And I mean, that's how we usually work in a big company, you have a big feature, an epic, and that is split into multiple issues and tasks which a few developers can work on in parallell. It really feels like Fable is built towards this kind of work, but as an orchestrator, when it was time to implement it could easily spin up multiple opus or sonnet agents depending on the work and implement the issues in parallell. After they where done we ran our usual workflow for PRs and it got merged to the dev branch in a clean manner.
Alright, I guess I've ranted long enough, have a cookie πͺ!
ππ