Agent skill · operations · sickn33
ask-matt
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Why this skill is useful
Codifies a structured workflow for navigating skills, which the AI could infer but now has a clear standard to follow.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Ask Matt When to Use Use when this workflow matches the user request: Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo. Source: mattpocock/skills (MIT). You don't remember every skill, so ask. A flow is a path through the skills. Most paths run along one main flow, and two on-ramps merge onto it. Everything else is standalone. The main flow: idea → ship The route most work travels. You have an idea and want it built. 1. /grill-with-docs — sharpen the idea by interview. Start here when you have a codebase: it's stateful, retaining what it learns in CONTEXT.md and ADRs. (No codebase? Use /grill-me — see Standalone.) 2. Branch — can you settle every question in conversation? If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by /handoff in both directions (see Crossing sessions): /handoff out, then open a fresh session against that file, /prototype to answer the question with throwaway code, /handoff back what you learned, and reference it from the original idea thread. 3. Branch — is this a multi-session build? Yes → /to-prd (turn the thread into a PRD) → /to-issues (split the PRD into independently-grabbable issues). Because the issues are independent, clear context between each one: start a fresh session per issue and kick off /implement by passing it the PRD and the single issue to work on. No → /implement right here, in the same context window. Context hygiene Keep steps 1–3 in one unbroken context window — don't compact or clear until after /to-issues — so the grilling, PRD, and issues all build on the same thinking. Each /implement then starts fresh, working from the issue. The limit on this is the smart zone: the window (~120k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before /to-issues, don't push on degraded — /handoff and continue in a fresh thread. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/ask-matt--423b28