ask-matt

Describe your current situation and the router maps it to a skill or flow. Ideas in a working directory route to /grill-with-docs, incoming bug reports route to /triage, and large foggy projects route to /wayfinder.

The main flow runs /grill-with-docs to sharpen the idea, optionally detours through /prototype for runnable questions, then /to-spec and /to-tickets for multi-session builds, and finally /implement per ticket with /code-review before committing.

Clear when the current context is irrelevant to what comes next, since it is the cheapest move. Compact when the context stays relevant, you are in the same harness and directory, and you need to stay in the loop; it is the default at the bottom of the decision tree.

Use /handoff only when work must travel: a new harness, a new directory, a colleague, or forking a side task mid-phase. Use a subagent when a tightly scoped task can run unattended and report back to the same session.

The router only selects among skills present in the repository and does not execute the work itself. Its phase-boundary decisions are judgement calls, so the same boundary can reasonably go two ways depending on context.