What problem does it solve? DevRel budgets are usually inherited from last year, priced only in cash, and ranked by whichever pillar is easiest to measure, so plans fail on uncounted staff hours and indefensible splits. This Skill turns a funded strategy into a line-item allocation where every line carries a cash cost, an hours cost, a return threshold, a review date, and a pre-agreed consequence if it misses. ## Core Features & Use Cases - Envelope and hours accounting: Sorts the budget into committed, discretionary, borrowed, and in-kind buckets, then totals real staff hours with a 20-30% capacity deduction before any line is priced. - Allocation shapes and thresholds: Brainstorms two or three whole-budget archetypes (enablement-first, content-compounding, field-and-events, community-led, ecosystem), ranks lines on effort rather than cost-per-unit, and sets baseline-derived thresholds per line. - Defense and cut planning: Ships a 10-20% reserve, an unfunded list, a ruled-out list, review clocks, reallocation triggers, and an ordered cut list for 20% and 40% reduction scenarios. - Use Case: A DevRel lead with 180K EUR and 2.5 FTE asks how to split it across events, content, and community, and receives a full allocation table with owners, thresholds, a reserve, and a five-sentence narrative the VP can repeat to finance. ## Quick Start Ask the assistant to split your developer relations budget for next year, stating the total amount, whether salaries are included, your team members and their weekly hours, and your funded driver.
