What problem does it solve? RedSkills ships dozens of slash commands across planning, execution, review, and operations, and remembering which one fits a given situation is hard. This Skill acts as a router: it classifies the current situation and returns the smallest useful flow of commands to run, in order. ## Core Features & Use Cases - Situation classification: Routes work by repository ownership and working mode (interactive, ADR-editing, spec-driven, ad-hoc) before naming a command. - On-ramp routing: Maps common situations — incoming bugs, parked human decisions, manual implementation slices, validation, daemon status, design uncertainty — to the right entry command such as /afk, /go, /triage, /hitl, or /diagnose. - Structured route answers: Returns a route in the form /first -> /second -> /final with the starting command, a one-sentence rationale, and the handoff condition for the next step. - Use Case: An operator asks "a reproducible bug just came in, what do I run?" and receives the route /diagnose -> /triage -> /afk with the condition that must hold before each handoff. ## Quick Start Ask which RedSkills flow fits your current situation, for example what command to run for a new bug report or a parked ticket.