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
Designed to assist users with ADHD (Attention Deficit Hyperactivity Disorder) by mitigating task paralysis, managing distractions, providing dopamine-driven progress tracking, and using executive-friendly visual formatting. Triggered by keywords or topics: - Focus/Distraction: "adhd", "fokus", "distracted", "gampang bosan", "pecah fokus", "distraksi", "sulit konsentrasi". - Task Initiation/Paralysis: "bingung mulai", "task paralysis", "mager", "banyak tugas", "tumpuk", "stuck", "overwhelmed". - Motivation/Rewards: "dopamine", "reward", "game", "poin", "xp", "checkpoint". - Formats: "bionic reading", "visual salience", "micro-step", "body double".
Execute detailed plans in batches with review checkpoints
Prevent task duplication, file conflicts, and coordination failures when multiple subagents work in parallel on the same Superagent project. Covers both Superagent→Subagent coordination and Master Agent→Superagent worktree coordination. Uses manage_plan and manage_tasks as the coordination hub.
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
Create isolated git worktrees with smart directory selection and safety verification
Triggered when the agent needs to audit, discover, and resolve missing features, architectural or functional gaps, performance/process bottlenecks, and structural complexity liabilities across a codebase, delivering lean and pragmatic improvement blueprints.
| 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 |
| author | mattpocock |
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-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.)/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-with-docs./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.
/grill-me — the same relentless interview as /grill-with-docs, but for when you have no codebase. Stateless: it saves nothing locally, builds no CONTEXT.md. Reach for it to sharpen any plan or design that doesn't live in a repo./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.