Route engineering requests to the right skill or flow

Ask Matt is a router over the user-invoked skills in Matt Pocock's skills repository. You do not remember every skill, so you ask, and it tells you which skill or flow fits your situation. A flow is a path through the skills. Most paths run along one main flow, two on-ramps merge onto it, and everything else is standalone.

The main flow runs from idea to ship:

• /grill-with-docs sharpens the idea by interview and is the starting point when you have a codebase. It is stateful and keeps what it learns in CONTEXT.md and ADRs.
• If a question cannot be settled in conversation because it needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype: /handoff out, open a fresh session against that file, use /prototype to answer the question with throwaway code, then /handoff back what you learned.
• For a multi-session build, run /to-prd to turn the thread into a PRD, then /to-issues to split it into independently-grabbable issues. Because the issues are independent, clear context between each one and start a fresh session per issue, kicking off /implement with the PRD and the single issue. For a small job, run /implement in the same context window.

Context hygiene matters: keep steps one to three in one unbroken context window and do not compact or clear until after /to-issues, so the grilling, PRD and issues build on the same thinking. The limit is the smart zone, roughly 120k tokens on state-of-the-art models, within which the model still reasons sharply. If a session nears it before /to-issues, use /handoff and continue in a fresh thread.

The rest of the map:

• On-ramp: /triage for bugs and requests piling up. It moves issues through triage roles and produces agent-ready issues that /implement later picks up. It is only for issues you did not create, and issues produced by /to-issues are already agent-ready, so do not triage them.
• Codebase health: /improve-codebase-architecture surfaces deepening opportunities whenever you have a spare moment. Picking one generates an idea to take into the main flow at /grill-with-docs.
• Crossing sessions: /handoff compacts the conversation into a markdown file so you can open a new session and reference it, in either direction. Built-in /compact stays in the same conversation and summarizes earlier turns, best at intentional breaks between phases and not mid-phase. /handoff forks while /compact continues.
• Standalone: /grill-me is the same relentless interview for when you have no codebase and saves nothing locally, /teach teaches a concept over multiple sessions using the current directory as a stateful workspace, and /writing-great-skills is a reference for writing and editing skills.
• Precondition: run /setup-matt-pocock-skills before your first engineering flow to configure the issue tracker, triage labels and doc layout the other skills assume. Custom issue trackers also work.

The input is a description of your situation, such as having an idea, a pile of bug reports, or no codebase. The output is a recommendation of which skill or flow to run next and in what order.

It routes across the slash-command skills in the repository and works with Claude Code, Codex CLI and Cursor.

Developers using coding agents who want a clear path from idea to shipped code, with guidance on when to hand off, compact or start a fresh session.