Skip to content

samber/dev-event-organizer-skills / skills/event-budget

event-budget

Verified

Build the budget and P&L for a technical event - every cost line split into fixed and per-head, the revenue mix against the funding model, a Good/Better/Best scope-tier ladder so break-even has three answers instead of one, a contingency sized as a stacked floor, pad and downgrade ladder whose cuts also price lost sponsor reach, a cross-edition reserve policy, annual funding decoupled from single events, and outflows scheduled against the dates sponsor and ticket money actually lands. Use whenever asked to build an event budget, model conference or hackathon costs, find break-even, size a contingency reserve, set a reserve or surplus policy across editions, fund a recurring meetup series annually, plan event cash flow, or decide what to cut when revenue falls short. Consumes prices and real vendor quotes, never sets them. Do NOT use to set ticket or sponsor prices - use samber/dev-event-organizer-skills@event-ticket-pricing or samber/dev-event-organizer-skills@event-sponsor-pricing.

evals/evals.json

View on GitHub
{
  "skill_name": "event-budget",
  "evals": [
    {
      "id": 1,
      "prompt": "I'm organizing KernelKraft Conf, a two-day community conference in Porto next June. 500 people have registered interest through our meetup group, and last year's similar events in our network saw about 78% of registrants actually turn up. We have one real number: a venue quote from October 14th covering the main hall plus two breakout rooms. Catering, AV, badges, swag - no quotes yet, so just fill in reasonable market prices so the board sees a complete budget. Our fiscal sponsor takes 8% of everything, and card processing fees are on top of that. We plan to announce the date publicly next week; the bank account through the fiscal sponsor isn't live yet, should be a few weeks out. Sponsors should cover most of the costs - so what should tickets cost to close the rest?",
      "expected_output": "A budget model that names the ticketed format and posture up front, budgets per-head lines off the ~390 expected show-up, carries the dated venue quote and explicit placeholders instead of invented prices, deducts the host share and processing fees off the top on both rails, defines a ticket revenue target for handoff rather than setting a price, costs three scope tiers with break-even each, schedules cash flow with its lowest point, flags the date announcement against the missing money-processing setup, and writes the tax question as a question.",
      "files": [],
      "expectations": [
        "The first line of the model names the format as ticketed and states the revenue posture assumed",
        "Per-head quantities are computed from the expected show-up figure (about 390), never from the 500 registrations",
        "Each cost line is classified fixed or per-head with its per-head driver named",
        "Speaker expenses are carried under a per-speaker driver, named as distinct from both fixed lines and per-attendee lines",
        "The venue line carries the dated October 14 quote",
        "Catering, AV, badges and swag are carried as explicit 'no quote yet' placeholders or ranges - no invented market prices despite the request to fill them in",
        "The fiscal sponsor's 8% share and card processing fees are deducted off the top, applied to both the ticket rail and the sponsor rail, before any cost line is funded",
        "No ticket price is set; instead a ticket revenue target (expenses minus the sponsorship share) plus paid capacity after comps is defined for handoff to ticket pricing",
        "Sponsorship is set as a share target for handoff to sponsor pricing; no tier split is produced here",
        "Three scope tiers (Good/Better/Best or equivalent) are each fully costed with a separate break-even",
        "A dated cash-flow schedule appears with its lowest cash point identified",
        "The response warns against announcing the date before a working way to process money exists, given the account is not live",
        "A total cost per head figure is computed from the fixed/per-head cut",
        "The tax and jurisdiction question is written as an open question routed to the fiscal sponsor or an accountant, not answered with a rate or rule"
      ]
    },
    {
      "id": 2,
      "prompt": "I'm treasurer for Datagrove Summit, a 400-person data engineering conference. Our board wants me to apply the standard industry contingency percentage to the budget before they sign off. I've seen 10% and 15% cited in event planning blogs - which one is the actual convention for conferences our size? We're a recurring annual event, third edition, and we kept our fully costed budget versions and per-line actuals from the last two years.",
      "expected_output": "A refusal to certify any percentage as an event-industry convention, replaced by a contingency built from three composing tools - an absolute cash floor, a pad on estimates labelled as borrowed from startup modelling, and a Good/Better/Best downgrade ladder with dated revenue checkpoints - with the ladder reused cheaply from prior editions and the resulting figure labelled self-set.",
      "files": [],
      "expectations": [
        "Declines to present any contingency percentage as an event-industry convention, stating no such convention exists",
        "Does not simply endorse 10% or 15% to satisfy the board",
        "Presents three contingency tools: an absolute floor, a pad on estimates, and a downgrade ladder",
        "The three tools are presented as composing together in one budget, with no ranking among them",
        "The floor is described as an absolute minimum cash reserve held regardless of budget size, not a percentage of budget",
        "The pad is explicitly labelled as coming from startup financial modelling rather than event practice",
        "The pad is described as protecting against line-item underestimation, distinguished from revenue shortfall",
        "The downgrade ladder is identified as the only tool that absorbs a whole-event revenue shortfall rather than a line-item miss",
        "The ladder is described as the scope tiers with dated checkpoints driven by revenue actually received",
        "The response notes that a recurring event with prior costed tiers can reuse them, making the ladder cheap this edition",
        "The final contingency figure is labelled self-set rather than published or standard",
        "Contingency drawn against contingency held across editions is proposed as the calibration read (never drawn suggests the floor is oversized; fully drawn suggests the pad is undersized)"
      ]
    },
    {
      "id": 3,
      "prompt": "TensorTide Conf is nine weeks out and sponsorship has landed at 55% of target. My co-organizer wants to act fast: cancel the venue contract and move to a cheaper space, and halve the catering order today. Current commitments: the venue is signed with a food-and-beverage minimum attached, the catering guarantee locks in three weeks, an evening afterparty is booked but cancellable free of charge until next month, and we budgeted a premium swag upgrade that hasn't been ordered yet. We also debated just bumping the ticket price 30% to cover the gap. What's the right sequence?",
      "expected_output": "A cut sequence that takes discretionary extras first, per-head quantities second within the three-week lock window, and fixed structural lines last; it rejects the venue switch as the most dangerous move because minimums are owed on the commitment, refuses the ticket price bump as a decision owned elsewhere, and anchors every cut to dates.",
      "files": [],
      "expectations": [
        "Discretionary extras - the afterparty and the swag upgrade - are cut first",
        "Per-head variable quantities (catering covers) come second, and only because the guarantee has not locked; the three-week lock date is cited as the window",
        "Fixed structural lines, the venue above all, come last in the sequence",
        "The co-organizer's venue-switch plan is rejected or flagged as the most dangerous move on the table",
        "Explains that food-and-beverage minimums and attrition are owed on what was committed, not on what turns up, so cancelling can cost more than it saves",
        "Does not assume the venue minimum can be renegotiated; committed minimums are treated as firm",
        "The cut sequence is anchored to dates from the cash-flow schedule, not stated in the abstract",
        "The 30% ticket price bump is refused as a pricing decision this analysis does not own; the ticket target is changed and handed to the pricing decision instead",
        "The cut order is framed as the content of the pre-priced scope-tier ladder, not invented as a fresh menu",
        "The catering cut is sized against the expected show-up figure and the lock date rather than an arbitrary halving today",
        "Warns explicitly that cutting a fixed line can produce a penalty larger than the saving",
        "Notes that once a lock date passes, the corresponding cut rung is gone",
        "No new revenue line is invented to balance the model"
      ]
    },
    {
      "id": 4,
      "prompt": "Compiler Days looks great on paper: projected 82k in revenue against 68k in costs. But I want a second opinion on the mechanics. The venue deposit of 40% is due March 15, the AV deposit April 1, insurance March 20. Our sponsor invoices go out when contracts sign in February, on net-60 terms, so we expect that money mid-May at the earliest. Tickets go on sale May 1. One vendor emailed offering us the option to pay their full balance now, no discount, 'to get it off your plate'. Are we fine?",
      "expected_output": "A dated cash-flow schedule showing the March-April outflows landing before any inflow, the lowest cash point identified in that gap, a warning that a profitable budget can still fail on cash, a refusal of the no-discount early payment as pure reversibility loss, and a latest-safe-date commitment posture with checkpoints.",
      "files": [],
      "expectations": [
        "States that the projected surplus does not answer the question - a budget can be profitable and still fail on cash",
        "Builds a dated schedule with each outflow on the date it leaves and each inflow on the date it lands",
        "Identifies the lowest cash point and places it in the window before sponsor money arrives mid-May",
        "Names the gap explicitly: deposits leave in March and April before any sponsor payment lands",
        "Ticket revenue is flagged as the latest-arriving line and the one that can miss",
        "The sponsor net-60 terms are treated as setting the inflow date the whole model rests on",
        "The vendor's pay-now offer is declined: with no early-payment discount on the other side, paying early spends recoverability and buys nothing",
        "Paying early is not framed as prudent or as getting ahead",
        "Recommends the latest-safe-date posture: identify, per commitment, the last date it can be made without losing the thing, and hold until then",
        "Raises fund-access timing: how long money takes to become spendable once it lands in the account",
        "Checkpoint dates for tracking revenue against the plan are produced",
        "Recommends re-reading the lowest cash point whenever a payment term changes, not only when a price changes",
        "The cost of the early payment is expressed as reversibility given up, not as a money amount"
      ]
    },
    {
      "id": 5,
      "prompt": "HackHarbor is our university's free 36-hour hackathon, 600 registrations so far. I need to work out how much to raise. My co-organizer says the fastest fix for our funding gap is a $10 entry fee - 'that's 6k right there'. Meanwhile I was going to order food for 600 for all five meal slots (Saturday lunch, Saturday dinner, midnight snack, Sunday breakfast, Sunday lunch), plus shirts for 600. We have about 40 mentors, volunteers and organizers on top of the participants. What should the budget look like?",
      "expected_output": "A free-by-construction model whose break-even is a fundraising target, rejecting the entry fee as a funding-model reversal, built on a food-dominant hackathon taxonomy with meal quantities tapered per slot instead of flat at 600, staff allocations added on top, overlooked tooling costs surfaced, and a flat scaled contingency floor presented as one organization's practice.",
      "files": [],
      "expectations": [
        "The first line names the model as free-by-construction, with break-even collapsing to a fundraising target rather than an attendee count",
        "The $10 entry fee is rejected as a funding-model reversal dressed as a budget adjustment, not adopted",
        "Ticket-line revenue postures are not ranked or offered for this event; sponsorship-by-construction is the named posture",
        "Total spend per head is identified as the main controllable lever",
        "A hackathon cost taxonomy is used with food as the dominant line, not a conference taxonomy",
        "Meal quantities are tapered per meal slot against a claim-rate curve rather than ordered flat at 600 for every slot",
        "Sunday breakfast is treated as the lowest-claim meal, on the order of a third of registrations rather than nearly all",
        "The roughly 40 mentor, volunteer and organizer meals are added on top of the attendee claim percentages, not assumed inside them",
        "Web hosting and internal tooling is surfaced as a commonly overlooked cost line, with student events able to source much of it free through education programs",
        "Shirt and swag quantities are driven by expected turnout rather than the 600 registration count",
        "The contingency includes a flat floor amount scaled to event size, presented as one organization's recommendation rather than an industry convention",
        "Each scope tier is expressed as a fundraising target",
        "A prizes line appears in the taxonomy, with a steer toward learning-value prizes over pure cash or its sizing routed to the prize-structuring decision",
        "The communication platform line is budgeted at zero or upgrade-only, reflecting a free base tier"
      ]
    },
    {
      "id": 6,
      "prompt": "Quayside DevCon's board is split on our sponsorship target. Director A read that a well-known open-source conference is 90% sponsor-funded and says we should match that. Director B found a standards body's published financial statement where cash sponsorship was only about 3% of revenue, and concludes tickets should carry us. Director C says the biggest community conference in our field generates about two-thirds of its parent foundation's total revenue, 'so 65% sponsor share is the norm'. We're a 350-person community conference and our tickets are mostly bought by attendees' employers as training. Settle this.",
      "expected_output": "An explanation that the published splits disagree because of structural choices and bound a range of postures rather than a norm - free-by-default attendance behind the 90%, in-kind contribution outside the 3% cash ratio, and a parent-organization dependency ratio misread as a revenue mix - followed by the posture menu with sponsor-led as default, the employer-training-budget condition engaged for registration-led, and the share set as a team-owned target handed onward.",
      "files": [],
      "expectations": [
        "States that published revenue splits disagree almost completely and bound the range of real postures, never a norm to hit",
        "The 90% figure is explained as a consequence of free-by-default attendance, not a target that event set",
        "The 3% cash figure is explained as understating sponsorship where a large in-kind contribution (space, network) sits outside the cash ratio",
        "Director C's two-thirds figure is identified as an event-to-parent-organization dependency ratio, not a within-event sponsor-to-ticket split",
        "No director's number is adopted as the target",
        "The three revenue postures are presented: sponsor-led, registration-led, sponsorship-by-construction",
        "Sponsor-led is named the default for a community conference, with sponsorship carrying the bulk and registrations covering per-attendee cost",
        "The registration-led promotion condition is engaged against the prompt's detail: the audience attends on employer training budgets, so registration-led is promoted or seriously weighed rather than dismissed",
        "Names what the default ordering starves - registration-led - and that following the default indefinitely makes the sponsor pool the event's ceiling",
        "The chosen share is framed as a lever the team sets, with the sponsorship target handed onward for tier-splitting rather than split here",
        "Registration-led is characterized as topping effort with its money landing latest",
        "Sponsor-led is credited with decoupling the decision to run from the ticket curve, which makes the downgrade ladder workable",
        "The three cited figures are not averaged into a blended market number"
      ]
    },
    {
      "id": 7,
      "prompt": "PortScan Summit runs under a fiscal sponsor - one of those open-source collective funding platforms. Our budget assumes their fee of 5% on card payments and 8% on bank transfers, which is what we remember signing up under. We sell tickets, and we have sponsors in Germany, Japan and the US; one sponsor wants a bundled package - sponsorship plus an expo booth as one line item at one price. Also: do we need to charge VAT on the tickets? And on the sponsorships? I'd rather set this up right than get audited.",
      "expected_output": "A model that flags the 5%/8% fee assumption as a superseded legacy structure to re-verify against current terms, situates the deduction in the typical 7-14% fiscal-sponsor range, takes host share and processing fees off the top on both rails, refuses to state any VAT rule while explaining tickets and sponsorship follow different jurisdiction-specific bases, recommends itemizing the bundled package, and writes the tax question with an owner and a date.",
      "files": [],
      "expectations": [
        "The 5%/8% fee assumption is flagged as a legacy structure that has been superseded, with instruction to verify the platform's current terms before budgeting on it",
        "The response notes the fee model behind those numbers changed recently (subscription-style model and/or an associated fiscal sponsor winding down), or at minimum that it cannot be assumed current",
        "The deduction is situated against the typical published fiscal-sponsor range of roughly 7-14%",
        "Host share and payment processing fees are deducted off the top, on both the ticket rail and the sponsor rail, before any cost line is funded",
        "No VAT rate, threshold, form name or registration rule is stated as though general",
        "States that ticket revenue and sponsorship revenue follow different, jurisdiction-specific tax bases",
        "Notes that sponsorship can face several tax treatments simultaneously when sponsors sit in different countries",
        "The tax question is written as a named open question with an owner and a date, routed to the fiscal host, a local accountant, or counsel",
        "Tax handling is carried as a named budget line",
        "The bundled sponsorship-plus-booth package is flagged: a bundle takes the treatment of its dominant element, so itemizing sponsorship and booth space separately is recommended",
        "Notes that any non-zero ticket price pulls in accounting and tax handling that a free event does not carry",
        "No specific named fiscal host, accounting platform or ticketing platform is recommended",
        "Fund-release timing from the fiscal sponsor is raised: how fast money can actually be spent once it lands",
        "No invented tax answer for Germany, Japan or the US appears anywhere in the response"
      ]
    },
    {
      "id": 8,
      "prompt": "Ferrite Forum planning, two things. First, I'm drafting our sponsor invoicing plan and used the standard structure - small deposit on signing, balance due 30 days before the event - since that's what everyone does. Should late payers owe us interest automatically? Second, the conference hotel offered us a courtesy room block: 60 rooms across three nights including the night after the closing day, no charge to hold it, and I'm inclined to lock all 60 now so attendees get the group rate. Anything wrong with this picture?",
      "expected_output": "A correction on both fronts: the small-deposit structure is a fallback pattern while real published sponsor terms skew 50-100% upfront; interest is owed only under an express clause whose drafting belongs to the agreement work; and the room block should start small, scoped to the nights genuinely needed with the post-event night dropped, grown as it fills, because a courtesy block can carry a usage guarantee owed on the commitment.",
      "files": [],
      "expectations": [
        "The small-deposit-then-balance-at-30-days structure is flagged as a generic fallback pattern, not a verified market standard",
        "States that real published sponsor payment terms skew heavily upfront, with 50-100% due at signing or application",
        "Recommends invoicing terms that land sponsor cash earlier, tied to the dates the cash-flow model needs money in the account",
        "States there is no automatic right to late-payment interest without an express contract clause",
        "Drafting the interest clause is routed to the sponsor agreement work rather than done here",
        "Any interest figure cited is presented as observed contract terms in the low-to-mid teens percent per annum, not as an entitlement or standard",
        "A sponsor signing and then paying late is framed as moving the inflow date the cash-flow model rests on",
        "Locking all 60 rooms now is rejected: the block should start very small, on the order of five rooms, and grow as it fills",
        "The block is scoped to the nights genuinely needed, explicitly dropping the night after the closing day",
        "Warns that a courtesy block can carry a usage guarantee, around 80% of blocked room-nights, owed on the commitment regardless of turnout",
        "The group-rate code expiry, roughly a month before the event, is carried as a date in the plan",
        "The asymmetry is stated: adding rooms later is cheap and usually allowed, while unwinding a committed block is expensive or impossible"
      ]
    },
    {
      "id": 9,
      "prompt": "Solder & Substrate Conf, edition two. Three things from our planning meeting. 1) Comps: a director wants us to reserve 5% of capacity as scholarship tickets 'because that's what the big conferences allocate'. 2) Reporting: our treasurer plans to report budget performance to the board as one number - 'we landed 2% under budget overall' worked fine last year. 3) Risk: two anchor sponsors provided 70% of our sponsorship last edition and both are 'probably renewing'. We still have last year's three costed budget versions, the per-line actuals, and the cash-flow projection on file. Set up edition two's money model approach.",
      "expected_output": "An edition-two setup that counts comps from agreements actually held instead of a capacity ratio, reports variance per line instead of one netted total, compares projected against actual cash troughs to separate inflow-date optimism from cost error, models the two-sponsor concentration through the tier ladder without booking probable renewals, reuses last edition's tiers with their calibration basis, and re-labels every carried line as quote or placeholder.",
      "files": [],
      "expectations": [
        "The 5%-of-capacity comp rule is rejected; comps are counted from agreements actually held - signed sponsor allotments, confirmed speakers, organizers, volunteers",
        "Any large-conference aid figure is treated as an order-of-magnitude sanity check (a low single-digit share of capacity), never an allocation rule",
        "Single-total variance reporting is rejected: variance is reported per line, because one total nets underestimates against overestimates and teaches nothing",
        "The lowest projected cash point is compared against the lowest actual cash point from last edition",
        "The diagnosis is split correctly: an actual trough far below projection means the inflow dates were optimistic, a different fix from the costs being wrong",
        "The 70%-from-two-sponsors concentration is treated as a budget risk, with the model stating what happens if the largest two do not renew",
        "The scope-tier ladder is named as the mechanism that answers the non-renewal question, which a single budget cannot",
        "'Probably renewing' is not booked as committed revenue",
        "Last edition's costed tiers are reused, making the ladder near-free this edition",
        "Per-head consumable lines rewritten from actual usage carry their calibration basis: the headcount and staff/volunteer/speaker composition they were priced against",
        "Contingency drawn against contingency held is read across editions as a calibration signal",
        "Which tier the event actually ran at versus which was planned is tracked as an observable",
        "Every line carried into edition two still requires a current dated quote or an explicit 'no quote yet' label; last year's prices are not silently treated as this year's quotes"
      ]
    }
  ],
  "trigger_queries": [
    { "query": "Build the budget for our 300-person developer conference in Lisbon next spring.", "should_trigger": true },
    { "query": "We're running a hackathon that's free to attend - how do I figure out how much we need to raise from sponsors?", "should_trigger": true },
    { "query": "What's our break-even attendee count if sponsorship covers most of the fixed costs?", "should_trigger": true },
    { "query": "How big should the contingency reserve be for a first-year tech conference?", "should_trigger": true },
    { "query": "Sponsorship is 30% below target with ten weeks to go. What do we cut first?", "should_trigger": true },
    { "query": "The venue wants a 40% deposit in February but our sponsor invoices won't be paid until May. Are we going to run out of cash?", "should_trigger": true },
    { "query": "Put together a P&L for the second edition of our Kubernetes community conference.", "should_trigger": true },
    { "query": "Which of our conference costs scale with headcount and which are fixed?", "should_trigger": true },
    { "query": "Model our conference finances across a cheap version, a normal version, and a stretch version.", "should_trigger": true },
    { "query": "How do I plan when money actually leaves and arrives for my conference?", "should_trigger": true },
    { "query": "Our fiscal host takes a cut of everything - how do I account for that in the event budget?", "should_trigger": true },
    { "query": "I have a venue quote and nothing else. Turn it into a full conference budget.", "should_trigger": true },
    { "query": "Catering, badges, swag - how many of each should we budget for if 800 people registered?", "should_trigger": true },
    { "query": "What happens to our event finances if our two biggest sponsors don't renew?", "should_trigger": true },
    { "query": "Draft the money model for a two-day community conference funded mostly by sponsors.", "should_trigger": true },
    { "query": "We collected 45k in sponsor commitments - is that enough to run the event, and what scope can we afford?", "should_trigger": true },
    { "query": "Help me work out the fundraising target for our student hackathon.", "should_trigger": true },
    { "query": "How much cushion should we hold on top of the event budget?", "should_trigger": true },
    { "query": "The AV company offered to invoice us now, months early - should we just pay it?", "should_trigger": true },
    { "query": "Is our conference financially viable at 250 paid attendees?", "should_trigger": true },
    { "query": "Lay out the cash-flow schedule for our conference so we know the worst month.", "should_trigger": true },
    { "query": "How should I split the conference budget between fixed commitments and per-attendee spend?", "should_trigger": true },
    { "query": "The board wants three budget scenarios for the summit before approving anything.", "should_trigger": true },
    { "query": "We need to know by what date sponsor money must land or we can't pay the venue.", "should_trigger": true },
    { "query": "Our devcon looks profitable on paper but I'm nervous about the deposit dates. Sanity-check the money.", "should_trigger": true },
    { "query": "What does it cost per attendee to run our event, all-in?", "should_trigger": true },
    { "query": "Budget planning for a 400-person DevOps conference, mostly sponsor funded.", "should_trigger": true },
    { "query": "If ticket sales come in slow, what's our financial fallback plan for the conference?", "should_trigger": true },
    { "query": "How do non-refundable deposits fit into the event's financial plan?", "should_trigger": true },
    { "query": "Deposits leave in March, sponsor payments land in June - how do I bridge the gap without a loan?", "should_trigger": true },
    { "query": "What share of our conference funding should come from sponsors versus registrations?", "should_trigger": true },
    { "query": "We overspent last year's conference - build this year's budget so that doesn't happen.", "should_trigger": true },
    { "query": "How do I turn last edition's actuals into next edition's event budget?", "should_trigger": true },
    { "query": "Estimate what our 48-hour hackathon will cost for 500 participants.", "should_trigger": true },
    { "query": "Should we order food for everyone who registered for the conference?", "should_trigger": true },
    { "query": "Someone said hold 10% back for surprises - is that right for a conference budget?", "should_trigger": true },
    { "query": "How do I budget for a free community event with no ticket revenue?", "should_trigger": true },
    { "query": "Our treasurer wants a proper financial plan for the conference, not just a spreadsheet of guesses.", "should_trigger": true },
    { "query": "Work out what we can afford to spend on the evening party without endangering the core event.", "should_trigger": true },
    { "query": "The venue contract has a food-and-beverage minimum - how does that change our budget risk?", "should_trigger": true },
    { "query": "Plan the finances for a 150-person unconference.", "should_trigger": true },
    { "query": "What do we do financially if we only hit 70% of the sponsorship target?", "should_trigger": true },
    { "query": "I need an event budget I can defend to our fiscal sponsor's board.", "should_trigger": true },
    { "query": "How much of our event spend is recoverable if we have to cancel two months before the date?", "should_trigger": true },
    { "query": "Give me the full cost breakdown for running a regional Python conference.", "should_trigger": true },
    { "query": "What financial setup do we need in place before announcing the conference date?", "should_trigger": true },
    { "query": "Balance our conference budget: 60k in expected expenses, sponsors have pledged 35k so far.", "should_trigger": true },
    { "query": "Growth team decided we're doubling capacity next year - redo the conference numbers at the new scale.", "should_trigger": true },
    { "query": "How do processing fees and the fiscal host's percentage affect what we can actually spend on the event?", "should_trigger": true },
    { "query": "Track our conference spending against the plan through the ticket sale window.", "should_trigger": true },
    { "query": "When can we safely commit to the catering guarantee for our summit?", "should_trigger": true },
    { "query": "Our hackathon budget: what line items am I forgetting?", "should_trigger": true },
    { "query": "Figure out whether the conference budget can absorb a second day of catering.", "should_trigger": true },
    { "query": "Convert these vendor quotes into a working event budget with scenarios.", "should_trigger": true },
    { "query": "What financial checkpoints should we set between now and doors open?", "should_trigger": true },
    { "query": "How exposed are we if attendance comes in 20% under the catering guarantee?", "should_trigger": true },
    { "query": "We committed to quantities before we knew how many people would really show up and it burned us last year - help me plan this edition's numbers better.", "should_trigger": true },
    { "query": "What should we charge for early-bird tickets at our conference?", "should_trigger": false },
    { "query": "How much should the Gold sponsorship tier cost?", "should_trigger": false },
    { "query": "Design our sponsorship tier ladder with price anchoring.", "should_trigger": false },
    { "query": "Write the sponsorship prospectus for our conference.", "should_trigger": false },
    { "query": "Draft the payment and late-fee clauses for our sponsor contract.", "should_trigger": false },
    { "query": "Find us a venue for 400 people and negotiate the rental terms.", "should_trigger": false },
    { "query": "Get three catering quotes for our conference.", "should_trigger": false },
    { "query": "Build the month-by-month work-back plan from today to doors open.", "should_trigger": false },
    { "query": "Set up the risk register for our conference.", "should_trigger": false },
    { "query": "What overbooking ratio should we use for free registrations?", "should_trigger": false },
    { "query": "Run the retrospective on last month's conference, including what went over budget.", "should_trigger": false },
    { "query": "Should our conference add a second track next year or move to a bigger venue?", "should_trigger": false },
    { "query": "Should we run a hackathon alongside our conference or keep them as separate properties?", "should_trigger": false },
    { "query": "How do we launch the first edition of a conference from zero?", "should_trigger": false },
    { "query": "Should our event be a single-day or multi-day conference?", "should_trigger": false },
    { "query": "Is there enough demand for a Rust conference in our city to sell it out?", "should_trigger": false },
    { "query": "How big should the hackathon prize pool be and how should it split across places?", "should_trigger": false },
    { "query": "Should we incorporate as a non-profit or use fiscal sponsorship for our meetup group?", "should_trigger": false },
    { "query": "Who at our company should own the developer conference budget line, marketing or DevRel?", "should_trigger": false },
    { "query": "Pick which sponsors to approach and write the outreach emails.", "should_trigger": false },
    { "query": "Deliver the booth and logo placements our Platinum sponsor was promised.", "should_trigger": false },
    { "query": "What perks should each sponsor tier include?", "should_trigger": false },
    { "query": "Plan the food and drink service style for our 300-person conference.", "should_trigger": false },
    { "query": "How many volunteers do we need and on what shifts?", "should_trigger": false },
    { "query": "Write the call for papers for our conference.", "should_trigger": false },
    { "query": "Set the ticket refund policy for attendees who can't make it.", "should_trigger": false },
    { "query": "Build the marketing plan to sell out our conference.", "should_trigger": false },
    { "query": "When should tickets go on sale and at what price steps?", "should_trigger": false },
    { "query": "Forecast our ticket sales pace and tell me if we're on track against the curve.", "should_trigger": false },
    { "query": "Pick the best date for our conference next year.", "should_trigger": false },
    { "query": "Plan my startup's annual marketing budget.", "should_trigger": false },
    { "query": "Help me budget my department's cloud spend for next year.", "should_trigger": false },
    { "query": "Build a personal budgeting spreadsheet for me.", "should_trigger": false },
    { "query": "Create a film production budget for a short documentary.", "should_trigger": false },
    { "query": "Budget for my wedding - 120 guests, outdoor venue.", "should_trigger": false },
    { "query": "How should I pace my ad budget across the quarter?", "should_trigger": false },
    { "query": "Draw up a construction project budget with a contingency allowance.", "should_trigger": false },
    { "query": "What's a sensible burn rate and runway model for my startup?", "should_trigger": false },
    { "query": "Estimate COGS and gross margin for our SaaS pricing tiers.", "should_trigger": false },
    { "query": "Set up cost alerts and budgets in our AWS account.", "should_trigger": false },
    { "query": "How do I run zero-based budgeting for my team's opex?", "should_trigger": false },
    { "query": "Model break-even for our new product line.", "should_trigger": false },
    { "query": "Plan the agenda and activities for our 40-person company offsite.", "should_trigger": false },
    { "query": "Negotiate better payment terms with our venue.", "should_trigger": false },
    { "query": "What AV setup do we need for recording the talks?", "should_trigger": false },
    { "query": "Reconcile the conference bank statements from last quarter.", "should_trigger": false },
    { "query": "Write the code of conduct for our event.", "should_trigger": false },
    { "query": "How do we get a big cloud vendor to sponsor our conference?", "should_trigger": false },
    { "query": "Design the judging rubric for our hackathon.", "should_trigger": false },
    { "query": "What swag should we produce for attendees this year?", "should_trigger": false },
    { "query": "Plan a travel reimbursement policy for our open-source maintainer program.", "should_trigger": false },
    { "query": "Set the speaker honorarium and travel coverage policy for invited keynotes.", "should_trigger": false },
    { "query": "Help me apply for a community grant to fund our meetup series.", "should_trigger": false },
    { "query": "What ROI report should we send sponsors after the event?", "should_trigger": false },
    { "query": "Build a dashboard to track event registrations and no-shows.", "should_trigger": false },
    { "query": "How much should exhibitors pay per square meter of booth space?", "should_trigger": false },
    { "query": "Estimate the token budget for our LLM evaluation pipeline.", "should_trigger": false }
  ]
}
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall