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: describe where you are (a vague idea, a bug, a pile of incoming requests, a huge foggy project) and it maps you to the right skill or flow. ## Core Features & Use Cases - Main flow routing: Maps the standard idea-to-ship path through grilling, prototyping, spec writing, ticket splitting, implementation, and code review. - On-ramp selection: Directs bugs to diagnosis, incoming requests to triage, and large foggy efforts to a decision-mapping flow. - Phase boundary guidance: Provides an ordered decision tree for choosing between continue, clear, handoff, subagent, or compact at the end of a work phase. - Use Case: You have a half-formed feature idea and a working repo. Ask which skill fits, and you are routed to the stateful grilling flow that sharpens the idea and records decisions in CONTEXT.md before implementation begins. ## Quick Start Ask which skill fits your current situation, for example by describing that you have a vague feature idea in a working directory and want to know where to start.
