Menu
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a researched, durable, approval-gated goal contract whose verification tools, repository-vault authentication, exact proof steps, rollout safety, and evidence lifecycle are ready before execution. Use when the user asks to set, create, refine, save, or verify a goal; asks whether an agent has everything needed to prove completion; wants a proof-driven alternative to a raw `/goal`; or explicitly invokes `$verify-goal`.
Relentlessly interview the user in dependency-aware batches to sharpen a plan, decision, design, idea, codebase change, or bug fix. Use when the user wants to get grilled, investigate a bug from a ticket or screenshots, pass unfinished grilling to a teammate, or pick it up from a PR. Begin each session by choosing native dialogs or one full text batch, then Sideshow or experimental Grill Visuals for live diagrams. In repositories, inspect current behavior, run a mandatory gap and blast-radius pass, and maintain durable decision docs as answers settle.
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked via Task after a parent gathers diff and file contents. Loads the rubric from the `thermo-nuclear-code-quality-review` skill in the cursor-team-kit plugin.
Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach upstream. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push safely, asks you to do a task and then validate it, or invokes /no-mistakes.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Configure this repo for the engineering skills โ set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
| name | ask-matt |
| description | Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo. |
| disable-model-invocation | true |
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 route most work travels. You have an idea and want it built.
/grill-me โ sharpen the idea by interview. It inspects code and maintains canonical plans, CONTEXT.md, and ADRs when a repository is present; otherwise it keeps a standalone decision log./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./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./implement right here, in the same context window.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.
A starting situation that generates work, then merges onto the main flow.
Bugs and requests piling up โ /triage. It moves issues through triage roles and produces agent-ready issues, which /implement later picks up.
Triage is only for issues you didn't create โ bug reports, incoming feature requests, anything that arrives raw. Issues that /to-issues produced are already agent-ready, so don't triage them.
Not feature work โ upkeep.
/improve-codebase-architecture โ run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces deepening opportunities; picking one generates an idea you can take into the main flow at /grill-me./handoff โ when a thread is full or you need to branch off (e.g. into a /prototype session), this compacts the conversation into a markdown file. You don't continue in place โ you open a new session and reference that file to carry the context across. It's the bridge between context windows, in either direction. Use it when you want a fresh session but need the current conversation preserved./compact (built-in) โ stay in the same conversation, letting the earlier turns be summarized. Use it at intentional breaks between phases, when you don't mind losing the verbatim history. Don't compact mid-phase โ the agent can lose its way. /handoff forks; /compact continues.Off the main flow entirely.
/teach โ learn a concept over multiple sessions, using the current directory as a stateful workspace./writing-great-skills โ reference for writing and editing skills well./setup-matt-pocock-skills โ run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.