Ask Brain

You don't remember every skill, so ask. This skill turns a task into a route: one skill, or an ordered chain.

How to route

1. Read the task. Match it to an intent in the routing table below. If it spans several intents, use a chain from Common chains.
2. Check preconditions. Engineering skills that touch the tracker need setup-optimal-brain first; vault skills need setup-knowledge-vault (or setup-optimal-brain with a vault); loops need setup-agent-loops. If .agent/context/ already has the config, skip setup.
3. Answer in this shape:
   • Route: skill or skill-a → skill-b → skill-c
   • Why: one line per step, tied to the user's task.
   • Skip: skills that look relevant but aren't, and why (e.g. "skip triage: these issues came from to-issues and are already agent-ready").
   • Start with: the exact first command to run.
4. Ambiguous? Ask one clarifying question (usually: "Is there a codebase?" or "Is this one session or several?"), then route. Never ask more than one.
5. Recommend only skills in the table. Don't invent skills. If nothing fits, say so and suggest the closest one.

Routing table

Every skill in the pack appears here exactly once as a row. Model-invoked skills (no slash needed) are marked auto; the agent applies them on its own when the situation matches.