What problem does it solve? Coordinators spawning multiple agents need a consistent, predictable way to pick the right LLM model for each task without manually specifying it every time, while still honoring persistent user preferences. ## Core Features & Use Cases - Five-Layer Resolution Hierarchy: Resolves models in priority order from persistent config overrides, session directives, agent charter preferences, task-aware auto-selection, down to a hardcoded default. - Persistent Preferences: Saves defaultModel and per-agent agentModelOverrides to .squad/config.json so choices survive across sessions. - Task-Aware Auto-Selection: Maps task types to tiers, sending code work to claude-sonnet-4.6, visual analysis to claude-opus-4.6, and docs or triage to claude-haiku-4.5. - Tier-Constrained Fallback Chains: Retries within the same tier when a model is unavailable, never falling up from fast to premium. - Use Case: A user says "always use opus for Fenster"; the skill validates the model ID, writes the override to config.json, and every future spawn of that agent acknowledges the resolved model. ## Quick Start Ask the coordinator to set a default model, for example by saying "always use claude-sonnet-4.6 for everything", and it will save the preference and apply it to all future agent spawns.