ask-matt

Routes development situations to the appropriate skill or workflow in the repository.

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill ask-matt-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.agents/skills/ask-matt
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill ask-matt-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a repository contains many AI skills, it is hard to remember which one fits the current situation. This Skill acts as a router that maps your starting situation (a raw idea, a bug, a huge foggy project, a merge conflict) to the right skill or flow. ## Core Features & Use Cases - Main flow routing: Guides work from idea to ship via /grill-with-docs, /to-spec, /to-tickets, /implement, /tdd, and /code-review. - On-ramp selection: Directs bug reports to /triage, broken behavior to /diagnosing-bugs, and large greenfield efforts to /wayfinder. - Phase boundary decisions: Provides an ordered decision tree (Continue, /clear, /handoff, subagent, /compact) for managing context between work phases. - Use Case: You have a vague feature idea and a pile of incoming bug reports. Ask which skill fits, and get routed to /grill-with-docs for the idea and /triage for the reports. ## Quick Start Ask which skill or flow fits your current situation, such as routing a new feature idea or a stubborn bug to the right workflow.

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 coding task?▼

Describe your starting situation, such as a raw idea, an incoming bug report, or a large foggy project. The router maps it to a main flow, an on-ramp like /triage or /diagnosing-bugs, or a standalone skill like /grill-me.

What is the main flow from idea to shipped code?▼

The main flow runs /grill-with-docs to sharpen the idea, optionally /to-spec and /to-tickets for multi-session builds, then /implement per ticket, which drives /tdd internally and finishes with /code-review before committing.

When should I compact context instead of clearing it?▼

Compact when the context is still relevant, you are in the same harness and directory, and you need to stay in the loop. Clear only when everything in the session is disposable, and prefer continuing whenever the next phase needs the current reasoning.

When should I use triage versus to-tickets for issues?▼

Use /triage only for issues you did not create, such as external bug reports and raw feature requests. Tickets produced by /to-tickets are already agent-ready, so they go straight to /implement without triage.

What are the limitations of a skill router?▼

A router only selects among skills that exist in the repository; it does not perform the underlying work itself. It also relies on judgement calls at phase boundaries, so the same boundary can reasonably go two ways.