Ask Matt answers the question of which skill to reach for. It maps the repository’s skills into one main flow from idea to ship, two on-ramps (incoming issues and broken code), a codebase health step, a vocabulary layer and a set of standalone tools.
You invoke it yourself. Before it states what a skill does or recommends skipping a step, it reads that skill’s SKILL.md.
What You Get
- A main flow from idea to ship: grill-with-docs, an optional prototype detour, to-spec and to-tickets for multi-session builds, then implement or implement-spec, code-review and retro
- On-ramps for triage, diagnosing-bugs and wayfinder that merge onto the main flow
- Guidance on context hygiene: when to continue, clear, hand off, use a subagent or compact at a phase boundary
- Short descriptions of standalone skills such as grill-me, prototype, research, wizard, wait-what and teach
Common Use Cases
- Starting a feature and not knowing which skill to run first
- Deciding between implement for each ticket and implement-spec for a whole spec
- Choosing what to do with the context window between the phases of a session
What Makes It Unique
Most skill collections list their skills. Ask Matt lays them out as flows with branch points, such as whether a question needs a runnable prototype or whether a build spans several sessions, and it names the order to run them in. It also points to PHASE-BOUNDARIES.md, a five-question tree for choosing between continue, clear, handoff, subagent and compact.
Under The Hood
The skill is one Markdown document that the model reads when you invoke it by name; automatic model invocation is disabled in its frontmatter. It runs no scripts and calls no services. It links to PHASE-BOUNDARIES.md for the phase-boundary decision tree, and it tells the model to read each recommended skill’s SKILL.md before describing it.