What problem does it solve? Developer relations programs often run as activity lists with no funded driver behind them, so they survive exactly one budget review. This Skill turns scattered DevRel activity into a one-to-two-page charter that names the business driver, caps the goals, picks the pillar mix, and states what the program refuses to do. ## Core Features & Use Cases - Structured interview and CORE analysis: Gathers the funding driver, stage, capacity, deadline, and effort ceiling, then writes Community, Organization, Relationships, and Ecosystem paragraphs before proposing anything. - Program shape selection: Brainstorms two or three whole-program archetypes (enablement-first, reach-first, community-first, and others), ranks them on efficiency, value, and effort axes, and deletes shapes the constraints rule out. - Build-vs-buy and staffing decisions: Decides in-house, contractor, agency, or community-sourced per bet with red lines for credibility surfaces, and names the next hire with its trigger instead of a twelve-month org chart. - Use Case: A first DevRel hire at a Series A API company needs a board-ready plan in eleven weeks; the Skill interviews them, recommends enablement-first, and produces a charter with three to five bets, each with an owner, signal, and review date. ## Quick Start Ask the assistant to design a developer relations strategy and charter for your company, describing your product, stage, team capacity, and who funds the program.
