ask-matt

Routes a described situation to the matching skill or workflow in this repository.

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill ask-matt-marjorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/archive/0-matt/ask-matt
Command: npx skills add https://github.com/marjorg/setup --skill ask-matt-marjorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you have many skills installed, remembering which one fits your current situation is hard. This Skill acts as a router: describe your situation and it maps you to the right skill or multi-step flow. ## Core Features & Use Cases - Skill routing: Maps your situation (new idea, bug, huge foggy project, merge conflict) to the correct skill such as /grill-with-docs, /diagnosing-bugs, /wayfinder, or /resolving-merge-conflicts. - Flow guidance: Explains the main idea-to-ship flow (grill, spec, tickets, implement, review) plus on-ramps like triage and bug diagnosis. - Phase boundary decisions: Provides an ordered decision tree for choosing between Continue, /clear, /handoff, subagent, or /compact at the end of a work phase. - Use Case: You have a vague feature idea and a pile of incoming bug reports; ask which skill to start with and get directed to /grill-with-docs for the idea and /triage for the reports. ## Quick Start Ask which skill fits your current situation, for example: I have a half-formed feature idea and don't know where to start, 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 task?

Describe your situation to the router and it maps you to a skill: new ideas go to /grill-with-docs, incoming bug reports to /triage, broken behavior to /diagnosing-bugs, and huge foggy projects to /wayfinder. Standalone needs like merge conflicts or prototyping have their own entry points.

What is the main idea-to-ship workflow for AI coding agents?

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 closes with /code-review before committing.

When should I compact vs clear vs handoff an agent session?

Decide only at a phase boundary using the ordered tree: continue if the next phase needs this context, /clear if the context is irrelevant, /handoff only for portability across harnesses or directories, subagent for AFK tasks, and /compact as the default fallback.

Should I triage tickets created by /to-tickets?

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

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

Use /wayfinder only for efforts too big and foggy for one session, like greenfield projects, where it charts decision tickets on the issue tracker. For ideas you can hold in one session, /grill-with-docs is faster and sufficient.