explaingit

orionmilos0-jpg/fabletieredworkflow

Analysis updated 2026-05-18

16ShellAudience · developerComplexity · 3/5Setup · moderate

TLDR

A Claude Code configuration that routes planning and review to one model and heavy implementation to others, cutting token costs on larger coding tasks by about 80 percent.

Mindmap

mindmap
  root((tiered-workflow))
    What it does
      Routes tasks by model
      Saves API tokens
      Coordinates subagents
    Tech stack
      Claude Code agents
      Fable Opus Sonnet
      Shell install script
    Use cases
      Plan then implement
      Second opinion review
      Shared run logging
    Audience
      Claude Code developers
      Cost conscious teams

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Automatically split a coding task across a planning model, an implementation model, and a test writing model to save tokens.

USE CASE 2

Get a second, independent review of AI generated code changes using the Codex CLI from a different model family.

USE CASE 3

Keep a shared run log so multiple AI subagents stay coordinated on the same task without losing context.

What is it built with?

ShellClaude CodeFableOpusSonnet

How does it compare?

orionmilos0-jpg/fabletieredworkflowai-engineer-skool/zen-agentic-engineer-configali-expandings/mactune
Stars161616
LanguageShellShellShell
Setup difficultymoderateeasyeasy
Complexity3/52/51/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires access to multiple specific AI models on your plan, and optionally a separate Codex CLI install.

License is not stated in the provided material.

In plain English

This project is a drop-in configuration package for Claude Code, Anthropic's coding assistant, that sets up multiple specialized subagents which automatically use different AI models depending on the kind of work being done. The idea is that expensive, careful reasoning should only be spent where it matters, while repetitive or high volume work goes to cheaper models, cutting token costs by roughly 80 percent according to the author. It defines four roles. An architect, powered by the Fable model, plans and breaks down a task and writes handoff instructions but never writes code itself, so its context stays clean. A developer, powered by Opus, does the actual heavy implementation work including the build, fix, and retry cycle. A test writer, powered by Sonnet, handles boilerplate tests, mocks, and fixtures. A reviewer, also powered by Fable, reads the finished changes and reports back a verdict without making edits itself. There is also an optional integration with OpenAI's Codex tool as a second, independent reviewer from a different model family, meant to catch issues the main models might miss. Three practices keep the setup working well: the architect must hand workers a clear, complete brief before routing work to them, everyone updates a single shared run log file so the reviewer can see what happened without piecing it together from chat history, and finished runs get archived into dated files instead of piling up and adding to every future run's reading load. Installation copies a set of agent definition files and a slash command into either a single project's .claude folder, shared with the whole team through version control, or into the user's global Claude Code configuration for use across every project. Once installed, typing a single slash command with a task description triggers the whole pipeline automatically, or each tier can be invoked one step at a time for closer control. It requires access to Fable, Opus, and Sonnet models on the user's plan, and optionally the separately installed Codex CLI tool. This is aimed at developers already using Claude Code who want to reduce API costs on larger coding tasks.

Copy-paste prompts

Prompt 1
Show me how to install this tiered workflow into my existing repo using install.sh.
Prompt 2
Explain the difference between the architect, developer, test writer, and reviewer roles in this workflow.
Prompt 3
How do I run the /tier slash command to delegate a task across the tiered model workflow?
Prompt 4
Walk me through the archive and drain ritual for keeping RUN-STATE.md from growing too large.

Frequently asked questions

What is fabletieredworkflow?

A Claude Code configuration that routes planning and review to one model and heavy implementation to others, cutting token costs on larger coding tasks by about 80 percent.

What language is fabletieredworkflow written in?

Mainly Shell. The stack also includes Shell, Claude Code, Fable.

What license does fabletieredworkflow use?

License is not stated in the provided material.

How hard is fabletieredworkflow to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is fabletieredworkflow for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.