What problem does it solve? When a repository contains many skills for grilling, speccing, ticketing, implementing, and reviewing work, it is hard to remember which one fits the current situation. This Skill acts as a router that maps your situation to the right skill or flow. ## Core Features & Use Cases - Main flow routing: Guides work from idea to ship through /grill-with-docs, /to-spec, /to-tickets, /implement, /tdd, and /code-review. - On-ramp selection: Directs bug reports to /triage, broken behavior to /diagnosing-bugs, and huge foggy efforts to /wayfinder. - Phase boundary decisions: Explains when to continue, /clear, /handoff, spawn a subagent, or /compact between phases of work. - 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 before speccing and implementation. ## Quick Start Ask which skill fits your current situation, for example: I have a multi-session feature to build, where do I start?