ask-matt

Routes users to the appropriate skill or workflow for their scenario.

2|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/skills --skill ask-matt-iskenkenya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/IsKenKenYa/skills/tree/main/skills/engineering/ask-matt
Command: npx skills add https://github.com/IsKenKenYa/skills --skill ask-matt-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a repository contains dozens of skills, it is hard to remember which one fits your current situation. This Skill acts as a router that maps your scenario—an idea to build, a bug to diagnose, a pile of incoming issues—to the right skill or multi-step flow. ## Core Features & Use Cases - Main flow routing: Guides idea-to-ship work through /grill-with-docs, /to-spec, /to-tickets, and /implement, with branching for prototypes and multi-session builds. - On-ramp selection: Directs bug reports to /triage, broken behavior to /diagnosing-bugs, and foggy large efforts to /wayfinder. - Phase boundary decisions: Explains when to continue, /clear, /handoff, spawn a subagent, or /compact between work phases, with a detailed decision tree in PHASE-BOUNDARIES.md. - Use Case: You have a vague feature idea and a repo full of skills. Invoke this Skill to learn that you should start with /grill-with-docs, then move to /to-spec and /implement. ## Quick Start Ask which skill or workflow fits your current task, for example by saying you have a new feature idea and want to know where to start.

Frequently Asked Questions about ask-matt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right skill for my task?

Invoke the ask-matt router and describe your situation, such as a new idea, a bug, or incoming requests. It maps your scenario onto the main flow or an on-ramp and names the specific skill to run first.

What is the main flow from idea to shipped code?

The main flow starts with /grill-with-docs to sharpen the idea, then branches to /to-spec and /to-tickets for multi-session builds or straight to /implement for smaller work. Each implementation ticket ends with /code-review before committing.

When should I use /compact versus /clear between phases?

Use /clear only when the current context is irrelevant to what comes next, since it is the cheapest reset. Use /compact when the context is still relevant but you need room, passing an instruction so the summary keeps what the next phase needs.

When should I use wayfinder instead of grill-with-docs?

Use /wayfinder for huge, foggy efforts like greenfield projects that cannot fit in one session, where it charts decision tickets on the issue tracker. Use /grill-with-docs for ideas you can sharpen within a single working session.

Can this skill be triggered automatically by the model?

No, it sets disable-model-invocation to true, so it only runs when the user explicitly invokes it. This keeps routing decisions under deliberate user control rather than implicit model activation.