domains / families / general / efficient-fable

efficient-fable

separate

Use when running Claude Fable on codebase-heavy or token-heavy work and the user wants Fable to orchestrate research, coding, and testing while cheaper subagents do bounded heavy lifting.

When to use

• orchestrating research, coding, and testing
• decomposing ambiguous work into parallel slices
• architecture, product, and safety tradeoffs
• integrating partial implementations
• final review, risk assessment, and synthesis
• delegating token-heavy tasks to cheaper subagents

When not to use

• tiny tasks
• tasks requiring delicate judgment for validation

Skill page

Source