skills.rest
The-Focus-AI
The-Focus-AIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ask-matt

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

Updated Jul 16, 2026
Search Tags:#workflow#context management#software development#decision tree#triage#skill router#phase boundary
One-click install
npx skills add https://github.com/The-Focus-AI/walking-thoughts --skill ask-matt-the-focus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/The-Focus-AI/walking-thoughts/tree/main/.agents/skills/ask-matt
Command: npx skills add https://github.com/The-Focus-AI/walking-thoughts --skill ask-matt-the-focus-ai

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 to the right skill or multi-step flow. ## Core Features & Use Cases - Main flow routing: Guides idea-to-ship work through grilling, prototyping, spec writing, ticket splitting, implementation, and code review. - On-ramp selection: Directs bug reports to triage, hard bugs to diagnosis, and large foggy efforts to the wayfinder mapping flow. - 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 fits, and get routed to triage for the reports and to the grilling flow for the idea. ## Quick Start Ask which skill or flow fits your current situation and describe what you are trying to accomplish.

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 starting situation and goal, and the router maps it to a skill or flow. Idea-to-ship work follows the main flow of grilling, spec, tickets, and implementation, while bugs and large efforts use dedicated on-ramps.

What is the main flow from idea to shipped code?▼

The main flow starts with grilling to sharpen the idea, optionally detours through a prototype, then produces a spec and tickets, and ends with implementation driven by test-driven development and code review.

When should I compact versus clear the context window?▼

Clear when the current context is irrelevant to what comes next, since it is the cheapest reset. Compact when the context remains relevant and you must stay in the same harness and directory, making it the default fallback at a phase boundary.

When should I use a handoff file instead of continuing?▼

Use a handoff only when switching harnesses, moving to a new directory or repository, sending work to a colleague, or forking a side task mid-phase. It buys portability; if nothing is travelling, continue in the current session.

Should incoming bug reports go through triage?▼

Yes, triage is for issues you did not create, such as bug reports and incoming feature requests. Tickets already produced by the ticket-splitting skill are agent-ready and should not be triaged again.

Related Skills

Explore More Software Engineering Skills→
jchildreejchildree
1

setup-scythe-skills

Configure repository engineering skills, issue tracker, triage labels, and documentation settings.

Community
Intermediate
MaxWolf-01MaxWolf-01
3

to-tickets

Breaks a grilled specification into dependency-ordered tracer-bullet ticket files with blocking edges.

Community
Advanced
shaahyshaahy

grill-with-docs

Interrogates a plan or design through structured questioning while generating ADRs and a glossary.

Community
Basic
AlexanderMattTurnerAlexanderMattTurner
64

git-workflow

Guides committing, pushing, and resolving merge conflicts in this repository.

Official
Advanced