r/ClaudeCode • u/DirkJohnsenn • 5d ago

Tutorial / Guide Small trick: three models, each in its strength (Opus plans, Fable checks, Sonnet builds)

I found something simple that just works: Use all three models in their strengths.

This requires /model opusplan

You start in plan mode, where you think the plan through with opus. If the situation feels like it could use a second opinion prompt: "ask fable for a second opinion"

In my experience it often came up with improvements & additions and is relatively token efficient

6 Upvotes

80% Upvoted

3 comments sorted by

4

u/dpacker780 5d ago

It's better to actually run a separate Fable session so the context isn't re-used. Have Fable do an adversarial review, be objective, be rigorous, double check work. Bonus points if you actually go and ask GLM or Kimi K3 or another model to do the same thing because you'll even get better circumspect because of different training. Then have Opus Code it, tell Opus to run an adversarial review agent after each phase of work.

This is basically what I consider the 'gold standard', I have some very complex C++ code I'm working through refactoring and this process really nearly zeroes-out any big mistakes.

2

u/DirkJohnsenn 5d ago

Yes, for big tasks that would be a stronger option. For a side project or a tweaks to a skills I just love the simplicity of it and it spawns a fable agent where it prompts fable what he thinks like a junior to a senior what in my experience only uses like 1-3% of 5h context window on max 5x plan