Detailed Analysis
A Reddit post in r/Anthropic surfaces a workflow tip that has gained traction among Claude power users: reserve "Fable" — evidently an internal or codename reference tied to a Claude model variant — for planning and architecture work, while routing actual code generation to Sonnet running in an "ultra code" mode. The poster's reasoning is pragmatic and economic: planning-heavy tasks consume fewer tokens than iterative code editing, so using a more expensive or capacity-constrained model exclusively for high-level design work preserves usage limits while still benefiting from that model's architectural judgment. The actual implementation is then handed to Sonnet, which the poster describes as producing clean code when constrained by both the upstream plan and the user's own markdown-based specification files.
This anecdote reflects a broader pattern that has emerged organically among developers using Claude Code and similar agentic coding tools: multi-model orchestration, where different Claude variants are assigned to different phases of the software development lifecycle based on their comparative strengths and the user's rate-limit economics. Rather than treating "the model" as a monolithic tool, sophisticated users are increasingly decomposing workflows into planning, scaffolding, implementation, and review stages, then matching each stage to whichever model configuration offers the best cost-to-quality tradeoff. This mirrors practices seen with tools like Claude Code's plan mode, where Anthropic has explicitly built support for separating a reasoning/planning pass from an execution pass — reducing the risk of a model diving into destructive edits without first establishing a coherent architectural approach.
The mention of supplementing model output with "your own md files" — markdown documents presumably containing project conventions, architecture decisions, or style guides — underscores a maturing best practice in AI-assisted development: treating the model's context window as a configurable environment rather than a black box. Users are learning that combining structural constraints (via markdown specs) with a dedicated planning pass measurably reduces the variance and risk of agentic coding sessions, colloquially described here as avoiding having something "bricked." This aligns with Anthropic's own guidance around Claude Code, which emphasizes providing persistent project context (e.g., CLAUDE.md files) to ground the model's behavior across long sessions.
More broadly, the post is a small but telling data point in the ongoing user-driven experimentation around agentic coding tools, where the community is effectively crowd-sourcing operational best practices faster than formal documentation can keep pace. As usage limits, token costs, and model capability differences become more salient to everyday users — not just enterprise customers — informal workflow patterns like "plan with one model, execute with another" are becoming as important to effective AI-assisted software development as prompt engineering itself. This trend suggests that as Anthropic and competitors continue to differentiate model tiers by reasoning depth versus raw throughput, users will increasingly demand — and build for themselves — orchestration layers that let them mix and match models within a single project rather than committing to one model for an entire task.
Read original article →