Fable plans and reviews while Sol codes to stretch subscriptions
A workflow gives planning to Fable, moves development work to Opus when the Fable allowance gets tight, and then uses Fable to look for weaknesses in the finished result. It has felt effective and produced satisfying results, but there are no measured comparisons of quality or cost.
Another proposed setup has Fable handle planning and design documents while writes the code. The aim is to divide work across paid Max and Pro allowances instead of paying separate .
The Fable allowance has already been exhausted twice, and any benefits or quality loss from the Sol setup remain untested. Concern that Anthropic might remove Fable also led to canceling the Max as a protest.
Key points
- Fable handled planning and the final check for weaknesses.
- Development moved to Opus when the Fable allowance became tight.
- An alternative setup gives design work to Fable and coding to .
- The goal is to use existing Max and Pro allowances instead of separate .
- The Fable limit was exhausted twice, and no measured comparison between the setups is available.