What problem does it solve? Multi-agent orchestration requires choosing the right LLM for every agent spawn, balancing cost, speed, and capability. Without a consistent resolution strategy, model choices become ad hoc, user preferences get lost between sessions, and spawn acknowledgments lack transparency about which model is running. ## Core Features & Use Cases - 5-Layer Resolution Hierarchy: Resolves models in first-match-wins order across persistent config overrides, session directives, charter preferences, task-aware auto-selection, and a hardcoded fallback. - 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 sonnet, visual analysis to opus, and docs or triage to haiku. - 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 spawn an agent for a coding task and confirm which model was resolved in the spawn acknowledgment.