Routes development situations to the appropriate skill or workflow in the repository.
npx skills add https://github.com/rockcookies/skills --skill ask-matt-rockcookies
Please help me install this Agent Skill. Skill: ask-matt Source: https://github.com/rockcookies/skills/tree/main/skills/mattpocock/ask-matt Command: npx skills add https://github.com/rockcookies/skills --skill ask-matt-rockcookies
/grill-with-docs, /to-spec, /to-tickets, and /implement, with branching decisions for prototypes and multi-session builds. - On-ramp selection: Directs bug reports to /triage, hard bugs to /diagnosing-bugs, and huge foggy efforts to /wayfinder. - Phase boundary decisions: Provides an ordered decision tree for choosing between Continue, /clear, /handoff, subagents, and /compact at phase boundaries. - Use Case: You have a vague feature idea and a working directory. Ask which skill fits, and get routed to /grill-with-docs to sharpen the idea, then onward to spec, tickets, and implementation. ## Quick Start Ask which skill or flow fits your current situation, describing whether you have an idea, a bug, incoming issues, or a large unclear project.High-intent search queries and answers about installing and using this skill.
Describe your starting situation — an idea, a bug, incoming requests, or a large unclear project — and the router maps it to a skill. Ideas go to /grill-with-docs, bugs to /diagnosing-bugs, and huge foggy efforts to /wayfinder.
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.
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.
No. Triage is only for issues you did not create, such as bug reports and incoming feature requests. Tickets produced by /to-tickets are already agent-ready and should go directly to /implement.
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 use the standard /grill-with-docs main flow instead.
Lev-itConfigure repositories with issue tracker settings, triage labels, and documentation structure.
B4rz99Automate implementation from specifications with test-driven development and code review.
haryelramalhoCreates CONTEXT.md glossaries and ADR files documenting architectural decisions and vocabulary per bounded context.
leeoveryGenerate a feature specification markdown file from inline context.