770a0504db
Ask Matt was missing five skills that now exist and are user-reachable: tdd (the red-green engine implement drives), diagnosing-bugs (there was no route for "something's broken"), domain-modeling and codebase-design (the two vocabulary references), and grilling (the shared primitive). - SKILL.md: add a "Something's broken" on-ramp for diagnosing-bugs, a "Vocabulary underneath" section for domain-modeling/codebase-design, weave tdd into the main flow, flesh out prototype, broaden the description from "user-invoked skills" to "the skills". - docs/engineering/ask-matt.md: re-sync the framing to match. - CLAUDE.md: add a maintenance rule so any future skill change triggers an Ask Matt re-check, beside the existing docs-page re-sync rule. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
31 lines
2.5 KiB
Markdown
31 lines
2.5 KiB
Markdown
Quickstart:
|
|
|
|
```bash
|
|
npx skills add mattpocock/skills --skill=ask-matt
|
|
```
|
|
|
|
```bash
|
|
npx skills update ask-matt
|
|
```
|
|
|
|
[Source](https://github.com/mattpocock/skills/tree/main/skills/engineering/ask-matt)
|
|
|
|
## What it does
|
|
|
|
`ask-matt` is the router over the skills in this repo. You describe the situation you're in; it tells you which skill or flow fits and in what order to run them.
|
|
|
|
It **does no work itself**. It doesn't grill, write a PRD, or fix anything — it only orients. It exists for the **user-invoked** skills above all: nothing fires those for you, so *you* have to remember they exist, and `ask-matt` is the memory you offload that to. It also points at the model-invoked skills you'd reach for by name — `/tdd`, `/diagnosing-bugs`, `/prototype`, `/code-review`, and the two vocabulary references, `/domain-modeling` and `/codebase-design`. It answers "which one, and when", then hands you off to the skill that actually does the job.
|
|
|
|
## When to reach for it
|
|
|
|
You invoke this by typing `/ask-matt` — the agent won't reach for it on its own.
|
|
|
|
Reach for it whenever you're unsure which skill or flow a situation calls for: you have an idea and don't know where to start, a pile of bug reports and don't know if they're for `/triage`, or two skills that look interchangeable and you can't tell them apart. If you already know the skill you want, skip the router and invoke it directly.
|
|
|
|
## Flows, not just skills
|
|
|
|
The idea `ask-matt` gives you to think with is the **flow** — a path *through* the skills rather than a single one. Most work runs along one **main flow** (idea → ship: grill → PRD → issues → implement → review), two **on-ramps** merge onto it (a triage lane for incoming bugs and requests; a codebase-health lane that generates ideas), and everything else is a **standalone** you reach for on its own. Ask a question and you get placed on the right flow, at the right step — not just handed a tool.
|
|
|
|
## Where it fits
|
|
|
|
`ask-matt` is the **router** — the standalone map that sits over the whole set. It is the node every other docs page links back to as [ask-matt](https://aihero.dev/skills-ask-matt), so it never sits *in* a chain; it points *into* every chain. From here you'll most often land on [grill-with-docs](https://aihero.dev/skills-grill-with-docs), the head of the main flow, or [triage](https://aihero.dev/skills-triage), the on-ramp for work you didn't create. When even the router's own picture is stale, its [Source](https://github.com/mattpocock/skills/tree/main/skills/engineering/ask-matt) is the map of record.
|