skills.rest
julianckt
juliancktCOMMUNITY
Explore all skills by this author →
GitHub

ask-matt

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

Updated Jul 31, 2026
Search Tags:#workflow#software engineering#context management#ai coding#skill router#flow selection
One-click install
npx skills add https://github.com/julianckt/adoptarun --skill ask-matt-julianckt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/julianckt/adoptarun/tree/main/.agents/skills/ask-matt
Command: npx skills add https://github.com/julianckt/adoptarun --skill ask-matt-julianckt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a repository contains many skills, it is hard to remember which one fits your current situation. This Skill acts as a router that maps your situation—an idea to build, a bug to fix, a pile of incoming requests—to the right skill or multi-step flow. ## Core Features & Use Cases - Flow routing: Describes a main flow from idea to shipped code (grill-with-docs, to-spec, to-tickets, implement) plus on-ramps for bugs, triage, and large foggy efforts. - Context hygiene guidance: Explains when to keep one context window, when to use handoff versus compact, and how to cross sessions without losing work. - Use Case: You have a vague feature idea and a codebase. Ask which skill fits, and you are directed to start with the grilling interview, then proceed through spec, tickets, and implementation. ## Quick Start Ask which skill or flow fits your current situation, describing whether you have an idea, a bug, or incoming requests.

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 situation—an idea to build, a bug to fix, or requests piling up—and the router maps it to a skill or flow. Ideas go through the main flow of grilling, spec, tickets, and implementation; bugs go to diagnosis; raw incoming issues go to triage.

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

The main flow starts with a grilling interview to sharpen the idea, optionally detours through a prototype for runnable questions, then splits into spec and tracer-bullet tickets for multi-session builds, and ends with test-driven implementation and code review per ticket.

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 triage flow?▼

Do not triage tickets that were already produced by the ticket-splitting step, since they are already agent-ready. Triage is only for issues you did not create, such as external bug reports and raw feature requests.

What skill handles very large or unclear projects?▼

The wayfinder flow handles huge, foggy efforts like greenfield projects by charting a shared map of decision tickets and resolving them one at a time. Once the map clears, it hands off to the spec step rather than building directly.

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
damoke012damoke012

ask-matt

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

Community
Intermediate
VrooliVrooli
54

Domain Compression

Compress overlapping domain concepts into a minimal consistent vocabulary.

Official
Advanced
leeoveryleeovery
27

start-feature

Generate a feature specification markdown file from inline context.

Community
Basic