ask-matt

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

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill ask-matt-sevwren
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/SevWren/Daily-Motivation-Brain-Helper/tree/main/CLAUDE/skills/engineering/ask-matt
Command: npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill ask-matt-sevwren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you have many skills available, it is hard to remember which one fits your current situation. This Skill acts as a router: describe where you are (a vague idea, a bug, a pile of incoming requests, a huge foggy project) and it maps you onto the right skill or flow. ## Core Features & Use Cases - Main flow routing: Guides idea-to-ship work through grilling, spec creation, ticket splitting, and TDD-driven implementation with code review. - On-ramp matching: Directs bug reports to triage, hard bugs to diagnosis with a tight feedback loop, and large foggy efforts to a wayfinding investigation flow. - Session management guidance: Explains when to hand off context to a fresh session versus compacting in place, and how to keep work inside the model's smart zone. - Use Case: You have a half-formed feature idea and a codebase. Ask which skill fits, and you are routed to the stateful grilling interview that builds CONTEXT.md, then onward to spec, tickets, and implementation. ## Quick Start Ask which skill fits your situation, for example: I have a vague feature idea and an existing codebase, 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 engineering task?▼

Describe your starting situation and this router maps it to a skill. Ideas with a codebase go to the stateful grilling interview, incoming bug reports go to triage, and large unclear efforts go to the wayfinding flow.

What is the main idea-to-ship workflow in this skill set?▼

The main flow runs grilling to sharpen the idea, then spec creation, then ticket splitting with blocking edges, then per-ticket implementation driven by TDD and closed out with code review.

When should I use handoff instead of compact?▼

Use handoff when you want a fresh session while preserving the current conversation as a markdown file. Use compact to stay in the same conversation at intentional phase breaks when losing verbatim history is acceptable.

Should I triage tickets that were already created from a spec?▼

No. Triage is only for issues you did not create, such as raw bug reports and incoming feature requests. Tickets produced by the ticket-splitting step are already agent-ready and go straight to implementation.

What skill fits a bug that resists a first glance?▼

Hard bugs, intermittent flakes, and regressions route to the bug-diagnosis skill. It requires a tight feedback loop, one command that already fails on this bug, before theorizing, then fixes with a regression test.