ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
romiluz13 · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add romiluz13/mifal --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.
Ask Matt
You don't remember every skill, so ask.
Before stating what a skill does or recommending a step be skipped, read that skill's SKILL.md: the summaries here are for orientation only.
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 inGLOSSARY.mdand ADRs. (No working directory? Use/grill-meinstead, covered under Standalone. Both run the same/grillingprimitive;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 what/handoffis 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), then/to-ticketsto split it into tracer-bullet tickets, each declaring its blocking edges. Then work the tickets one of two ways:/implementper ticket,/clearing context between each one. 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. Each ticket is self-contained, so the last one's context is disposable./implement-specfor the whole spec in one run. It reads the tickets as a task graph, runs implementer subagents across the ready frontier in parallel, and lands everything on one integration branch. Reach for it when you'd rather orchestrate the build than drive each ticket yourself.
- No →
/implementright here, in the same context window.
Either way, the code gets built by driving
/tdd(one red-green slice at a time) and closes out with/code-review, a two-axis review (Standards + Spec) of the diff./implementruns both per ticket;/implement-spec's implementers each drive/tdd, and it runs one/code-reviewover the integration branch. Reach for/tddon its own when you just want to build a concrete behaviour test-first without a full spec, and/code-reviewon its own whenever you want to review a branch or PR against a fixed point.When the work goes up as a pull request,
/prshapes the body: the smallest visual that shows the change, before/after evidence that it works, and a one-way or two-way door call. It's model-invoked, so the agent reaches for it whenever it writes a PR. - Yes →
-
/retrocloses the loop. After a build, and especially one that went sideways, it looks back over the session and suggests changes to the agent's environment, not the code: navigation pointers, automated checks, the coding standards/code-reviewenforces, steering files, tooling. Mechanical mistakes become deterministic checks; judgement calls become coding standards. The next build then starts from a better environment.
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. Run /retro in the session it's looking back on, before you clear; after clearing, point it at that session's log instead.
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, which/implementlater 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. Once the fix is in, run/retroin the same session to ask what would have prevented the bug; where the real finding is that there's no good seam to lock it down, that's a job for/improve-codebase-architecture. -
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