ask-matt

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

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill ask-matt-tajo9128
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/tajo9128/BioDockify-Pharma-AI/tree/main/.agents/skills/ask-matt
Command: npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill ask-matt-tajo9128

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a repository contains many skills for grilling, speccing, ticketing, implementing, and reviewing work, it is hard to remember which one fits the current situation. This Skill acts as a router that maps your situation to the right skill or flow. ## Core Features & Use Cases - Main flow routing: Guides work from idea to ship through /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 huge foggy efforts to /wayfinder. - Phase boundary decisions: Explains when to continue, /clear, /handoff, spawn a subagent, or /compact between phases of work. - 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 before speccing and implementation. ## Quick Start Ask which skill fits your current situation, for example: I have a multi-session feature to build, where do I 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 coding task?

Describe your situation and this router maps it to a skill: ideas go to /grill-with-docs, multi-session builds to /to-spec and /to-tickets, and single-session work straight to /implement. Bugs and incoming requests route to /triage or /diagnosing-bugs instead.

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, which drives /tdd internally and finishes with /code-review before committing.

When should I compact context versus clear or hand off?

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

Can I use this router outside a working directory?

Yes. When there is no repository, the router points you to stateless standalone skills like /grill-me instead of /grill-with-docs, since no CONTEXT.md or ADR paper trail can be maintained.

What are the limitations of a skill router?

The router only selects among skills present in the repository and does not execute the work itself. It also requires the /setup-matt-pocock-skills precondition to configure the issue tracker, triage labels, and doc layout other skills assume.