ade35dc0d8
The repeated "The load-bearing constraint:" opener on every page read as an agent tell. Strip the label across all skill pages and let the constraint stand as a plain declarative sentence; update the writing-docs template so it isn't regenerated. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2.3 KiB
Quickstart:
npx skills add mattpocock/skills --skill=ask-matt
npx skills update ask-matt
What it does
ask-matt is the router over every user-invoked skill 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. Because these skills are user-invoked, nothing fires them for you, so you have to remember they exist; ask-matt is the memory you offload that to. 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), 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, so it never sits in a chain; it points into every chain. From here you'll most often land on grill-with-docs, the head of the main flow, or triage, the on-ramp for work you didn't create. When even the router's own picture is stale, its Source is the map of record.