Routes engineering situations to the appropriate skill or workflow in the repository.
npx skills add https://github.com/MSC72m/DevForge --skill ask-matt-msc72m
Please help me install this Agent Skill. Skill: ask-matt Source: https://github.com/MSC72m/DevForge/tree/main/skills/ask-matt Command: npx skills add https://github.com/MSC72m/DevForge --skill ask-matt-msc72m
High-intent search queries and answers about installing and using this skill.
Describe your current situation and the router maps it to a skill or flow. Ideas in a working directory route to /grill-with-docs, raw bug reports route to /triage, and broken behavior routes to /diagnosing-bugs.
The main flow runs /grill-with-docs to sharpen the idea, optionally detours through /prototype for runnable questions, then /to-spec and /to-tickets for multi-session builds, and finally /implement per ticket with /code-review before committing.
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 the context stays relevant but the window is filling up.
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 should go straight to /implement.
Use /wayfinder for huge, foggy efforts like greenfield projects that cannot fit in one session, where it charts decision tickets on the issue tracker. For ideas you can hold in one session, /grill-with-docs is faster and sufficient.
Lev-itConfigure repositories with issue tracker settings, triage labels, and documentation structure.
j172Routes user situations to the appropriate skill or workflow in the repository.
VrooliCompress overlapping domain concepts into a minimal consistent vocabulary.
leeoveryGenerate a feature specification markdown file from inline context.
