ask-matt

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

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill ask-matt-kunj-sharma03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-matt
Source: https://github.com/Kunj-Sharma03/agent-contextify/tree/main/skills-main/skills/engineering/ask-matt
Command: npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill ask-matt-kunj-sharma03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a repository contains dozens of agent 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 foggy greenfield effort—to the right skill or multi-step flow. ## Core Features & Use Cases - Main flow routing: Guides work from idea to ship through /grill-with-docs, /to-spec, /to-tickets, and /implement, with branching for prototypes and multi-session builds. - On-ramp selection: Directs incoming bug reports to /triage, broken behavior to /diagnosing-bugs, and huge foggy efforts to /wayfinder. - Phase boundary decisions: Provides an ordered decision tree (Continue, /clear, /handoff, subagent, /compact) for managing context between work phases, detailed in PHASE-BOUNDARIES.md. - Use Case: You have a vague feature idea and a pile of bug reports. Ask which skill fits, and get routed to /triage for the reports and /grill-with-docs to sharpen the idea before implementation. ## Quick Start Ask the agent which skill or flow fits your current situation, describing what you are trying to do.

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 agent skill for my task?

Describe your situation—an idea to build, a bug to fix, or incoming requests—and the router maps it to a skill. Ideas go to /grill-with-docs, raw bug reports to /triage, and broken behavior to /diagnosing-bugs.

What is the main flow from idea to shipped code?

The main flow runs /grill-with-docs to sharpen the idea, then /to-spec and /to-tickets for multi-session builds, then /implement per ticket. Single-session work skips straight to /implement after grilling.

When should I use /compact versus /clear or /handoff?

Use /clear when the context is irrelevant to what comes next, /handoff only when moving to a new harness, directory, or colleague, and /compact as the default when context stays relevant. Continue is always ruled out first since it costs nothing.

When should I use /wayfinder instead of /grill-with-docs?

Use /wayfinder for huge, foggy efforts like greenfield projects that cannot fit in one session; it charts decision tickets on the issue tracker. Use /grill-with-docs for ideas you can hold in a single session.

Should I triage tickets created by /to-tickets?

No. /triage is only for issues you did not create, such as incoming bug reports and feature requests. Tickets produced by /to-tickets are already agent-ready and can go straight to /implement.