The sort of thing Fable and Sol excel at are long horizon tasks. The sort of thing I have been using them for is migrating large numbers of repositories to new tooling simultaneously (adopting new linters, enabling dependabot automerge, rolling out mutation testing).

Some of that can be done mechanically or trivially, and Fable knows to write a script or deploy Sonnet for those instances, but other times there are complications that need to be overcome that need to be escalated. Then there are patterns that can be picked up in large migrations and fed into template repos or tooling.

I won't use Fable for everything, but if there is ground to be broken on a new concept, being able to build a prototype with Fable might be useful.

I also have some substantive migration tasks such as replacing a static front end with solidjs or moving from NLL to Polonius that I would like to use Fable for.

It certainly feels like over the last fortnight it has enabled a substantial amount of transformative change in my codebases.

For my needs, Opus does these kind of "long horizon tasks" well enough already, with additional tooling.

As long as you are chunking out the tasks generated from the plan, you can manually (or write an orchestrator to...) give the component tasks to agents that pass along inputs and outputs per the dependency graph derived from the plan.

You can write this plan yourself or review it with the agent. Chunking tasks out of the plan like this has the added benefit of being able to swap for a different model when the time comes (looking forward to Opus-level models I can run on my consumer card...)

Not really convinced using Fable and trusting the harness to orchestrate for you is worth the intelligence upgrade. An understanding of an high level implementation plan of your task is also necessary when working with colleagues who rightfully quiz you. Especially since, at least for my work, there isn't a lot that Opus struggles with.