ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
gongyijie85 · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add gongyijie85/mattpocock-skills-dsh --skill ask-mattAbout this skill
name: ask-matt description: Ask which skill or flow fits your situation. A router over the skills in this repo. disable-model-invocation: true
Ask Matt
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, or a vocabulary layer that runs underneath.
The main flow: idea → ship
The route most work travels. You have an idea and want it built.
-
grill-with-docssharpens the idea by interview. Start here whenever you are working in a working directory: it's stateful, retaining what it learns inCONTEXT.mdand ADRs. (No working directory? Usegrill-meinstead, covered under Standalone. Both run the samegrillingprimitive;grill-with-docsis the one that leaves a paper trail, which makes it the better of the two whenever a repo is there to leave it in.) -
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
handoffin both directions (a prototype lives in its own directory, which is exactly whathandoffis for; see Phase boundaries):handoffout, then open a fresh session against that file,prototypeto answer the question with throwaway code,handoffback what you learned, and reference it from the original idea thread.
-
Branch: is this a multi-session build?
- Yes →
to-spec(turn the thread into a spec), thento-ticketsto split it into tracer-bullet tickets, each declaring its blocking edges. On a local tracker that's one file per ticket under.scratch/<feature>/issues/, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed: kick offimplementper ticket,/clearing context between each one. Each ticket is self-contained, so the last one's context is disposable. - No →
implementright here, in the same context window.
Either way,
implementbuilds each issue by drivingtddinternally (one red-green slice at a time), then closes out by runningcode-review, a two-axis review (Standards + Spec) of the diff, before committing. Reach fortddon its own when you just want to build a concrete behaviour test-first without a full spec, andcode-reviewon its own whenever you want to review a branch or PR against a fixed point. - Yes →
Context hygiene
Keep steps 1–3 in one unbroken context window (don't compact or clear until after to-tickets) so the grilling, spec, and tickets all build on the same thinking. Each implement then starts fresh, working from the ticket.
The limit on this is the smart zone: the window (~150k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before to-tickets, don't push on degraded; /compact at the nearest phase boundary and carry on (see Phase boundaries).
On-ramps
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, whichimplementlater picks up.Triage is only for issues you didn't create: bug reports, incoming feature requests, anything that arrives raw. Tickets that
to-ticketsproduced are already agent-ready, so don't triage them. -
Something's broken →
diagnosing-bugs. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a tight feedback loop (one command that already goes red on this bug), then fixes with a regression test. Its post-mortem hands off toimprove-codebase-architecturewhen the real finding is that there's no good seam to lock the bug down. -
A huge, foggy effort: a greenfield project or a huge feature build, too big for one session →
wayfinder, the most cognitively demanding flow here. When the way from here to the destination isn't visible yet, it charts a shared map of decision tickets on the issue tracker and resolves them one at a time, producing decisions, not deliverables, until the fog is pushed back and the way is clear. Wheregrill-with-docssharpens an idea you can hold in one session, wayfinder is for the idea you can't, and it's slower and denser, so save it for exactly that, never a well-scoped feature.When the map clears, it hands off, it doesn't build: merge onto the main flow at
to-spec, which collapses the map's linked decisions into a buildable plan, thento-ticketsandimplementas usual. Looping the map straight intoimplementskips that collapse and throws the linked detail away, so go straight toimplementonly when the effort turned out genuinely small.
Codebase health
Not feature work, just upkeep.
improve-codebase-architectureruns 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 atgrill-with-docs. It's the survey that finds the candidates;codebase-design(below) is the bench you design the chosen one on.
Vocabulary underneath
Two model-invoked references that run beneath the other skills, each the single source of truth for its vocabulary. Reach for them directly when the words, not the process, are the problem; or let the skills above pull them in.
domain-modeling: sharpen the project's domain language: challenge a fuzzy term, resolve an overloaded word ("account" doing three jobs), record a hard-to-reverse decision as an ADR. It's the active d