You should basically never use Fable for coding, but instead use it as a planner/orchestrator. Most of today's advanced models can implement a spec perfectly, and once done you can send the work to F
Why CEREBRO kept it
Fable as planner/orchestrator; novel pattern
The text below is an automated extraction of the article at https://x.com/skirano/status/2065096311410409770, stored verbatim in the public cerebro-vault repository. Copyright remains with the original publisher (x.com).
Most of today's advanced models can implement a spec perfectly, and once done you can send the work to F
> Fable as planner/orchestrator; novel pattern
You should basically never use Fable for coding, but instead use it as a planner/orchestrator.
Most of today's advanced models can implement a spec perfectly, and once done you can send the work to Fable to review.
This has been my most powerful flow so far.
Backlinks
Appeared in 1 briefing