The user does not know which skill fits their situation. Find the one that does.

Read the frontmatter (name and description) of every skill in this suite. The files sit next to this one: glob */SKILL.md from this skill's parent directory. Skills marked disable-model-invocation: true are hidden from your session registry, so the files are the source of truth, never your visible skill list.
If the situation is ambiguous between skills, ask one clarifying question. Otherwise ask nothing.
Answer with one skill, or a short ordered chain when the situation spans stages. Name the trigger (slash command or phrase). No menus.

When a chain is needed, the workflow order is: drill (fuzzy plan; domain terms settle here too) → implement (settled plan; debug owns anything that breaks along the way) → verify (before claiming done) → architecture (existing code fights you). Session utilities sit outside the chain: research, teach (user-only), huh (user-only), spawn (user-only), land, parallel, write-skill.

Never propose writing a new skill until step 1 has ruled out every existing one, including the hidden ones.

which-skill