Document model roles for feature work in CLAUDE.md

Codifies the plan-with-Fable / implement-with-Sonnet / review-with-Fable
split (Opus as fallback) for feature work and PR reviews.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Sean Whalen
2026-07-12 09:31:23 -04:00
co-authored by Claude Sonnet 5
parent 42059db935
commit 0d50cff388
+10
View File
@@ -2,4 +2,14 @@
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
## Model roles for feature work
Any new feature or modification to an existing feature must follow this model split:
1. **Plan with Fable** (fall back to Opus only if Fable is unavailable). Enter plan mode, design the implementation, and present the plan to the user for approval or modification. Do not start implementing until the user approves the plan.
2. **Implement with Sonnet.** Once the plan is approved, carry out the implementation using Sonnet (e.g. by delegating the implementation steps to Sonnet subagents via the Agent tool with `model: "sonnet"`).
3. **Review with Fable** (fall back to Opus only if Fable is unavailable). After implementation, all work must be reviewed by Fable before it is considered done.
**PR reviews** must also use Fable, with Opus as the fallback if Fable is unavailable.
@AGENTS.md