Elixir Skill Router

HARD-GATE

Non-negotiable: no implementation code until a test exists, runs, and fails for the right reason (feature missing, not config/syntax).

Routing priority

1. Playbook when the request is multi-step (TDD, bug fix, quality, setup, LiveView feature, Oban job, migration, PR review).
2. Atomic skill when the request is a single domain (Ecto query, channel auth, Credo config).
3. Code-producing work: if the next step writes .ex or .exs, load elixir-essentials together with the domain skill. It is not only a language-ambiguity fallback.
4. Ambiguity: inspect mix.exs, mix.lock, routes, and nearby code first. Language-only questions use elixir-essentials; Phoenix controller/API questions use their domain skills. Select LiveView only when the project and task use LiveView. Ask one scope question if the evidence cannot choose a workflow.
5. Small bugs: use bug-fix directly with a failing reproduction and minimal fix; a formal PRD is unnecessary. Resolve scope before writing tests for a new feature.

See assets/skill-map.json (mappings, defaults, disambiguation).