choosing-models

Choose which Claude model and effort a task should run on — a capacity-dispatch step when work is about to be delegated or priced. Use when spawning subagents or workflow agents, when authoring a governed multi-PR series file (e.g. a convoy series.toml governance block, and per-PR tiers where the engine supports them), when a planning tool asks for a per-task tier (a route-and-budget phase, per-role picks in an execution plan), when sizing a review panel's model ladder, or when deciding "is Haiku enough for this task?" / "which tier should this PR run at?". Scores the task with the bundled rubric, maps score to tier to current model via models.toml, then applies context modifiers (oracle coverage, reversibility, retry economics). Model facts — ids, prices, context windows, API mechanics — belong to the platform's model reference (e.g. the claude-api skill); this skill reads that data and owns only the task-to-tier routing policy. Not for choosing which skill owns a task (that is choosing-tools), not for toolkit inventory (that is toolkit-awareness), and not an in-run auto-escalation mechanism — escalation is an authoring or retry decision.