Ask Matt (routeur de skills)
You invoke /ask-matt when you no longer know which of the 25 skills to reach for. It is a router: it maps a main flow (idea to ship) running through /grill-with-docs, then /to-spec, /to-tickets, /implement, /tdd, /code-review, two on-ramps (/triage for piling bug reports, /diagnosing-bugs for what broke, /wayfinder for the foggy effort), a vocabulary layer (/domain-modeling, /codebase-design) and a list of standalone skills. It also documents phase boundaries: continue, /clear, /handoff, subagent, /compact.
Strengths
- An explicit decision tree, not a table of contents: each branch says when you take it and when you do not
- Documents the context hygiene (keep grilling, spec and tickets in one window) that the other skills assume without saying it
- Phase-boundaries section: five ordered options (continue, /clear, /handoff, subagent, /compact) with the reasoning behind each
- Marks the usage traps: do not triage a ticket /to-tickets just produced, do not pull /wayfinder on a well-scoped feature
Limitations
- Only routes Matt Pocock skills: it ignores everything else you installed, and your real mental map mixes both
- Volatility: the router names skills, an upstream rename (diagnose became diagnosing-bugs) makes it wrong until the update lands
- Never self-triggers (disable-model-invocation), so if you forget it exists you fall back to the three skills you know
Best for
- Devs who just installed the set and have no idea where to start
- Tech leads who want a shared team method without writing the process doc themselves
- Long sessions where you hesitate between compacting, clearing or handing off to a subagent