model-delegation

Solid

Initiate the orchestrator-worker cost model for this session. The main-loop model (expensive, metered) orchestrates, specs, verifies, and validates only; ALL drafting and mechanical work (code, docs, tests, sweeps, research) runs in Opus 4.8 subagents billed to plan allowance. Invoke at session start or whenever token cost matters.

AI & Automation 14 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
39
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Model delegation (orchestrator thinks, workers write) Purpose: when the main-loop model bills to metered usage credits and subagent models bill to a subscription plan, the expensive model must never do the writing. Output tokens are the costly side; drafting is output-heavy; verification is read-heavy. So the orchestrator reads and decides, the workers write. On invocation, adopt this operating mode for the rest of the session. ## Model policy | model | role | billing | |---|---|---| | main loop (e.g. Fable 5) | decompose, spec, review, validate, decide, talk to the user | metered credits, minimize output | | opus-4.8 subagents | write code/docs/tests, mechanical sweeps, research, exploration | plan allowance | | sonnet / haiku | never, regardless of task size | - | These are defaults with one standing override: if a worker's output does not meet the bar after one revision round, the orchestrator redoes that piece itself. Judge the output, not the price tag; escalating costs less than shipping mediocre work. ## Mechanics - Spawn workers via the Agent tool with `model: "opus"`. Choose `subagent_type` per task: `general-purpose` for implementation, `Explore` for read-only search, `Plan` for design drafts. - Independent tasks launch in ONE message so they run in parallel. - Workers mutating files in parallel get `isolation: "worktree"`. - Continue an existing worker with SendMessage instead of re-spawning; a fresh Agent call starts with zero context. - Multi-agent...

Details

Author
erhantez
Repository
erhantez/claude-fable-5-spanking-claude-opus-4.8
Created
1 weeks ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

subagent-delegation

Use BEFORE starting any multi-part task (research or comparisons across several sources, reading or summarizing long documents and transcripts, bulk updates across many items, audits, or checking a draft or numbers before they go out). Also use when about to spawn any subagent or worker, or when a task needs 3+ searches or tool calls. Routes gathering, reading, and bulk work to cheaper worker models, and escalates hard reasoning or a final check to a stronger model only when that actually helps.

0 Updated 6 days ago
alectivism
AI & Automation Listed

model-orchestration

Apply the fixed model-role and thinking-effort policy whenever work is delegated to subagents or a model/effort choice is made: the orchestrator (top-tier model) DIRECTLY sets service direction, reviews plan/spec documents (with multi-persona-review), improves shipped features, and hunts performance/security problems; plan/spec/planning documents are AUTHORED by Opus, which also owns core implementation and V&V, at xhigh or above; repetitive implementation and E2E tests go to Sonnet at high or above — never delegate below those effort floors. Use whenever you are about to spawn an Agent/Task/Workflow worker, pick a model for a subtask, set a thinking/effort level, assign verification, or hand off orchestration because the current model's quota is exhausted. Trigger on "위임해", "에이전트로 돌려", "오케스트레이션", "모델 역할분담", "어떤 모델로", "effort 얼마로", "thinking level", "서브에이전트", or in English "delegate this", "spawn an agent for", "which model should", "route this task", "verify with", "orchestrate". Fire even when the user does

3 Updated today
uzysjung
AI & Automation Listed

worker-budget

Use BEFORE spawning any Agent worker for substantial work (builds, audits, releases). Deterministic budget analysis — pricing snapshot, per-worker-class token forecast from observed history, tier recommendation, and a worker contract with success thresholds + orchestrator-escalation triggers. Also use when the user asks about worker costs, budget analysis, or model-tier selection.

0 Updated 2 days ago
esummervill