skills.rest
j172
j172COMMUNITY
Explore all skills by this author →
Website𝕏@j172GitHub

ask-matt

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

Updated Jul 30, 2026
Search Tags:#workflow#tdd#software engineering#code review#context management#triage#skill router
One-click install
npx skills add https://github.com/j172/bid --skill ask-matt-j172
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/j172/bid/tree/main/agent/skills/ask-matt
Command: npx skills add https://github.com/j172/bid --skill ask-matt-j172

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? With many skills available, it is hard to remember which one fits your current situation. This Skill acts as a router, mapping your starting point — a raw idea, a bug, a pile of incoming requests, or a foggy large effort — onto the right skill or sequence of skills. ## Core Features & Use Cases - Main flow guidance: Charts the idea-to-ship path through grilling, spec writing, ticket splitting, TDD implementation, and code review. - On-ramp routing: Directs bug reports to triage, hard bugs to diagnosis, and huge foggy efforts to the wayfinder mapping flow. - Session management advice: Explains when to hand off context between sessions versus compacting in place, and when to keep one unbroken context window. - Use Case: You have a vague feature idea and a codebase. Ask which skill to use, and get routed to the grilling interview, then through spec, tickets, and per-ticket implementation. ## Quick Start Ask which skill fits your situation, for example: I have a bug that only fails 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 the right skill for my task?▼

Describe your starting situation — an idea, a bug, incoming requests, or a large foggy effort — and the router maps it to the matching skill or flow. Ideas go to the grilling interview, raw bug reports to triage, and hard bugs to the diagnosis flow.

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

The main flow runs grilling to sharpen the idea, then to-spec to write a spec, to-tickets to split it into tracer-bullet tickets, and implement per ticket using TDD with a final code review. Single-session work skips the spec and tickets steps.

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 to reference. Use compact to stay in the same conversation at intentional breaks between phases when losing verbatim history is acceptable.

When should I not use the wayfinder flow?▼

Wayfinder is only for huge, foggy efforts where the path is not visible, such as greenfield projects. It is slower and denser than other flows, so well-scoped features should go through the standard grilling and spec flow instead.

Should I triage tickets created by to-tickets?▼

No. Triage is only for issues you did not create, such as external bug reports and feature requests. Tickets produced by to-tickets are already agent-ready and go straight to implementation.

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
taxmaxitaxmaxi
1

ask-matt

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

Official
Intermediate
vishirivishiri
401

fantasia-worldbuilding-domain

Align AI suggestions with Fantasia Archive's worldbuilding domain terminology and data models.

Community
Intermediate
leeoveryleeovery
27

start-feature

Generate a feature specification markdown file from inline context.

Community
Basic