What problem does it solve? When a repository contains dozens of skills, it is hard to remember which one fits the current situation. This Skill acts as a router: describe your situation and it maps you to the right skill or multi-step flow. ## Core Features & Use Cases - Main flow routing: Guides work from idea to ship via /grill-with-docs, /to-spec, /to-tickets, /implement, /code-review, and /to-pull-requests. - On-ramps and standalone skills: Directs bugs to /diagnosing-bugs, incoming requests to /triage, foggy large efforts to /wayfinder, and one-off needs to skills like /prototype, /research, or /wizard. - 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 repo. Ask which skill to use, and it routes you to /grill-with-docs to sharpen the idea, then onward to /to-spec and /to-tickets. ## Quick Start Ask the agent which skill fits your current situation, for example: I have a bug that only appears intermittently, which skill should I use?