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: describe where you are (an idea, a bug, a pile of requests, a foggy project) and it maps you onto the right skill or flow. ## Core Features & Use Cases - Main flow routing: Guides idea-to-ship work through /grill-with-docs, /to-spec, /to-tickets, and /implement, with branching rules for prototypes and multi-session builds. - On-ramp selection: Directs incoming bugs and requests to /triage, hard bugs to /diagnosing-bugs, and large foggy efforts to /wayfinder. - Context hygiene guidance: Explains when to keep one context window, when to use /handoff to cross sessions, and when to use /compact. - Use Case: You have a vague feature idea and a codebase but no plan. Ask this Skill, and it routes you to /grill-with-docs to sharpen the idea, then onward to spec, tickets, and implementation. ## Quick Start Ask which skill fits your situation, for example: I have a bug report and a half-formed feature idea, which skill should I start with?
