ask-matt

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

10|3|Updated Jul 18, 2019
One-click install
npx skills add https://github.com/tanqimin/MyFavsORM --skill ask-matt-tanqimin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/tanqimin/MyFavsORM/tree/main/.agents/skills/ask-matt
Command: npx skills add https://github.com/tanqimin/MyFavsORM --skill ask-matt-tanqimin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a repository contains many 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 pile of requests, a foggy greenfield effort) 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, hard bugs to /diagnosing-bugs, and huge foggy 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 working directory. Ask which skill to use, and get routed to /grill-with-docs to sharpen the idea, then onward to spec, tickets, and implementation. ## Quick Start Ask which skill fits your current situation, for example: I have a bug that only fails intermittently, which skill should I use?

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 current task?

Describe your starting situation, such as a raw idea, an incoming bug report, or a foggy large effort. The router maps it to a skill: ideas go to /grill-with-docs, external bug reports to /triage, and hard bugs to /diagnosing-bugs.

What is the main flow from idea to shipped code?

The main flow runs /grill-with-docs to sharpen the idea, then /to-spec and /to-tickets for multi-session builds, then /implement per ticket. Single-session work skips straight to /implement after grilling.

When should I use /compact versus /clear or /handoff?

Use /clear when the context is irrelevant to what comes next, /handoff only when moving to a new harness, directory, or colleague, and /compact as the default when the context stays relevant. Continue is always ruled out first since it costs nothing.

Should I triage tickets created by /to-tickets?

No. Triage is only for issues you did not create, such as incoming bug reports and feature requests. Tickets produced by /to-tickets are already agent-ready and go directly to /implement.

When is /wayfinder the right choice over /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. For ideas you can hold in one session, /grill-with-docs is the correct starting point.