ask-matt

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

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/PVMalove/claude-agent-harness --skill ask-matt-pvmalove
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/PVMalove/claude-agent-harness/tree/main/skills/first-party/pvmalove/ask-matt
Command: npx skills add https://github.com/PVMalove/claude-agent-harness --skill ask-matt-pvmalove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a repository contains dozens of skills, it is hard to remember which one fits the current situation. 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 - Main flow routing: Guides work from idea to ship via /grill-with-docs, /to-spec, /to-tickets, /implement, /code-review, and /to-pull-requests. - On-ramps and standalone skills: Directs bugs to /diagnosing-bugs, incoming requests to /triage, foggy large efforts to /wayfinder, and one-off needs to skills like /prototype, /research, or /wizard. - 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 repo. Ask which skill to use, and it routes you to /grill-with-docs to sharpen the idea, then onward to /to-spec and /to-tickets. ## Quick Start Ask the agent which skill fits your current situation, for example: I have a bug that only appears 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 which skill to use for a new feature?▼

Describe your situation and the router maps it to a flow. For a feature idea in a working directory, it points to /grill-with-docs first, then /to-spec and /to-tickets for multi-session builds, or straight to /implement for single-session work.

What skill should I use for a hard-to-reproduce bug?▼

Use /diagnosing-bugs for bugs that resist a first glance, intermittent flakes, or regressions. It requires a tight feedback loop that reproduces the bug before theorizing, then fixes it with a regression test.

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

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, a 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 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; it charts decision tickets on the issue tracker. Use /grill-with-docs for ideas you can sharpen within a single session.