using-exolisted

# Using exo A bare skill name in an exo skill, agent or rule means `exo:<name>`. ## Before acting 1. Invoke the skill whose description matches before the first tool call or clarifying question; when it turns out wrong, say so and leave it. 2. No skill for a version-only bump, a git-only operation, a read-only question no description claims, or an edit of at most two files adding no dependency and changing no public signature, persisted format or security boundary; at any file count an unproven failure still goes to `debug`, a visual change to `designing`, a test-first request to `implementing-batch`. 3. A push, pull request or merge runs through `shipping` and an issue through `issuing`, never by hand; the finish pick or a plain request authorizes it. ## When several fire - `debug` outranks the rest until a failure's cause is proven. - `shaping` decides what to build, `planning` orders it, `implementing` runs a plan, `implementing-batch` builds without one; the earlier stage wins. - `deepen` finds where the architecture should change; `shaping` shapes a change the request names. - `research`, `designing` and `skills-tool` hand control back to a stage that borrowed them and own the turn alone. - An instruction in CLAUDE.md or the prompt outranks a skill. # Right-sizing This ladder keeps complexity low by reusing what exists; it holds before every edit adding or replacing code, with no skill call. ## The ladder Read the ranges the change touches and trace their contro