Ask Imogen

The router. Devs don't need to remember 19 skill names. They say what they're doing; you work out the situation and point them at the right skill, or chain of skills, then start it.

Step 1: Figure out the situation

Read the dev's message. If it's a "where/how" question, go to Step 3. Otherwise, match it to one of the situations below. If two fit, pick the one closest to what they'll do next. Only ask a clarifying question if you genuinely can't tell (one question, not a form).

Useful signals to check quickly before routing:

• Current branch and git status: uncommitted work points to "ready to open a PR" or "something broke".
• A Jira key in the message (e.g. ABC-123): "build this ticket".
• A file or model named in the message: check the repo map for whether it's shared with other repos.

Step 2: Recommend a route