Route engineering requests to the right skill or flow

Ask Matt is a router over the user-invoked skills in mattpocock/skills (MIT licensed) - since you don't remember every skill, it asks which skill or flow fits your situation. A flow is a path through the skills: most work runs along one main flow, two on-ramps merge onto it, and a few skills are standalone.

Use it as the entry point when you're unsure which of the repo's skills to invoke next for your situation. It requires /setup-matt-pocock-skills to have been run first, to configure the issue tracker, triage labels, and doc layout the other skills assume (custom issue trackers also work).

The main flow runs idea to ship. /grill-with-docs sharpens an idea by interview when you have a codebase - it's stateful, retaining what it learns in CONTEXT.md and ADRs (use /grill-me instead with no codebase). If a question needs a runnable answer, work detours through a prototype bridged by /handoff in both directions, using /prototype to answer with throwaway code. A branch then decides whether this is a multi-session build: if yes, /to-prd turns the thread into a PRD, /to-issues splits it into independently-grabbable issues, and each issue gets a fresh session with /implement given the PRD and that single issue; if no, /implement runs right in the same context window. Steps 1-3 stay in one unbroken context window, without compacting or clearing, until after /to-issues - bounded by the model's "smart zone" (about 120k tokens on state-of-the-art models); a session nearing that limit before /to-issues should /handoff and continue fresh rather than push on a degraded context. Two on-ramps generate work that merges onto the main flow: /triage moves piled-up bugs and incoming feature requests (not issues /to-issues already made agent-ready) into agent-ready issues for /implement; and /improve-codebase-architecture, run for codebase upkeep rather than feature work, surfaces deepening opportunities that can seed a new idea back into /grill-with-docs. Two ways to cross sessions exist: /handoff compacts the current conversation into a markdown file and forks into a new session that references it, for when a thread is full or needs to branch; /compact (built-in) instead summarizes earlier turns within the same conversation, for intentional breaks between phases rather than mid-phase. Standalone skills off the main flow are /grill-me (the same interview as /grill-with-docs but stateless, for plans or designs with no codebase), /teach (learn a concept across multiple sessions using the current directory as a stateful workspace), and /writing-great-skills (reference for writing and editing skills well).

Anyone working across this skills repo who needs a router to decide which flow to enter - a fresh idea, a pile of incoming bugs, or a codebase health pass - and how to move context safely between sessions as the work grows.