ask-matt

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

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Avistian/nba --skill ask-matt-avistian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/Avistian/nba/tree/main/.agents/skills/ask-matt
Command: npx skills add https://github.com/Avistian/nba --skill ask-matt-avistian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a repo contains many user-invoked skills, it is hard to remember which one fits your current situation. This Skill acts as a router that maps your starting situation 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-prd, /to-issues, and /implement with context-hygiene rules. - On-ramps and standalone paths: Directs bug triage to /triage, codebase upkeep to /improve-codebase-architecture, and codebase-free planning to /grill-me. - Session bridging: Explains when to use /handoff versus /compact to carry context across sessions without losing work. - Use Case: You have a vague feature idea and a codebase; invoke this Skill to learn you should start with /grill-with-docs, then proceed to /to-prd and /to-issues before implementing. ## Quick Start Ask which skill fits your situation, for example: I have a pile of incoming bug reports and do not know where to 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 which skill to use for a new feature idea?▼

Start with /grill-with-docs if you have a codebase, since it sharpens the idea by interview and stores context in CONTEXT.md and ADRs. If you have no codebase, use /grill-me instead, which is stateless.

What is the difference between /handoff and /compact?▼

/handoff compacts the conversation into a markdown file so you can open a fresh session referencing it, forking the work. /compact stays in the same conversation and summarizes earlier turns, best used at intentional breaks between phases.

When should I use /triage versus /to-issues?▼

Use /triage only for issues you did not create, such as incoming bug reports and feature requests. Issues produced by /to-issues are already agent-ready and should go straight to /implement without triage.

Can I run the idea-to-ship flow across multiple sessions?▼

Yes, but keep grilling, PRD, and issue splitting in one unbroken context window until /to-issues completes. Then start a fresh session per issue for /implement, using /handoff if you approach the context limit early.

What should I run before using these workflow skills for the first time?▼

Run /setup-matt-pocock-skills before your first engineering flow. It configures the issue tracker, triage labels, and doc layout that the other skills assume, though custom issue trackers also work.