What problem does it solve? Developer-relations work spans documentation, open source, community, events, content, and program strategy, making it hard to know which skill applies to a given task. This Skill acts as the router for the 55-skill developer-relations-skills collection, matching the current task to exactly one sibling skill, naming coverage gaps honestly, and keeping project context warm between sessions via a devrel-context.md artifact. ## Core Features & Use Cases - Task routing: Matches the session goal against every sibling skill's declared scope and routes to exactly one, or states plainly that no skill fits and names the gap. - Cold and warm starts: Detects whether devrel-context.md exists, runs detection over the repository before asking questions, and caps the interview at 5-7 questions on a cold start or a single session-goal question on a warm start. - Prioritized output: Delivers a route, a 5-8 entry short-list ordered by value per unit of effort, an optional dependency-ordered chain, a not-now list with unblocking conditions, and named gaps. - Routines and memory: Proposes 2-4 scheduled or event-triggered routines with dry-run approval, and persists permitted facts to memory while excluding confidential items. - Use Case: A first DevRel hire at a startup asks what to do first; the Skill flags an unfocused strategy, chains developer-segmentation into devrel-strategy and devrel-metrics, and writes devrel-context.md for the next session. ## Quick Start Ask the assistant to kick off a new developer-relations project or run a DevRel check-in and route your current task to the right skill.
