What problem does it solve? When a repository contains many skills, it is hard to remember which one fits the current situation. This Skill acts as a router that maps your starting situation (a raw idea, a bug, a pile of requests, a foggy greenfield effort) to the right skill or multi-step 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 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 (Continue, /clear, /handoff, subagent, /compact) for managing context between work phases. - Use Case: You have a vague feature idea and a working directory. Ask which skill to use, and get routed to /grill-with-docs to sharpen the idea, then onward to spec, tickets, and implementation. ## Quick Start Ask which skill fits your current situation, for example: I have a bug that only fails intermittently, which skill should I use?