samber/dev-event-organizer-skills / skills/event-debrief
event-debrief
VerifiedRun the organizing team's own internal retrospective on one finished edition of a technical event - the blameless frame, the reconstructed timeline, what went well split from what went poorly, what fired reconciled against the risk register, budget plan and run of show, team-health findings, and dated lessons-learned entries each carrying an owner and a due date. Use whenever asked to run a post-event debrief, a post-mortem or a retrospective after a conference, meetup or hackathon, review an edition against the goals the team set, build a lessons-learned log, or publish a public recap. Do NOT use to collect participant feedback - use samber/dev-event-organizer-skills@event-feedback - or for trends across editions - use samber/dev-event-organizer-skills@event-continuous-improvement.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 28.0 KB |
| evals/evals.json | config | 31.6 KB |
| references/field-precedent.md | markdown | 6.0 KB |
| references/lessons-learned-entries.md | markdown | 5.1 KB |
| references/reconciliation-and-session-agenda.md | markdown | 7.7 KB |
evals/evals.json
View on GitHub{
"skill_name": "event-debrief",
"evals": [
{
"id": 1,
"prompt": "I co-organize PixelForge Summit, a 350-person indie game-dev conference in Leeds. This year's edition ended eight days ago and honestly nothing went wrong - talks ran on time, the budget landed where we planned it, zero incidents. The three of us on the core team are completely wiped out. My co-organizer says a debrief is only worth running when something actually breaks, like an outage post-mortem at work, so we should skip straight to planning, which kicks off in about five weeks. Is he right? And if not, what's the lightest version we could get away with?",
"expected_output": "A recommendation to hold the debrief anyway, explaining that incident-postmortem severity gating does not transfer to events, with a lightweight single-session or pre-read format sized to a three-person exhausted team, a date set immediately, and exhaustion itself logged as a finding.",
"files": [],
"expectations": [
"Recommends holding the debrief despite nothing going wrong, explicitly rejecting the idea that a debrief is gated on something breaking",
"States that the severity threshold from incident/outage postmortem practice does not transfer to recurring events",
"Justifies the debrief for a quiet edition by naming the risk that practices which worked but go unnamed get silently dropped next edition",
"Recommends setting and calendaring the debrief date immediately, before the team disperses, rather than deferring the scheduling decision",
"States that no standard interval after the event exists and proposes a concrete date anyway",
"Recommends a lightweight depth rung (single session, or written pre-read plus one session), not per-track or multi-track formats",
"Removes both track-based depth options entirely for the three-person team rather than merely ranking them lower",
"Names the team's exhaustion as a finding of the debrief itself, not merely a scheduling constraint to work around",
"Warns against manufacturing action items to look thorough, and allows an explicit 'no action, because [reason]' as a complete outcome",
"Requires every log entry to carry a named owner and a due date, or an explicit no-action",
"Treats the planning start in five weeks as the debrief's deadline and recommends writing open items into next edition's plan",
"Runs what-went-well and what-went-poorly as two separate passes with the well pass first, and does not compare this edition against previous editions"
]
},
{
"id": 2,
"prompt": "TrailStack Conf (400 attendees, single day) ended Saturday and I'm turning our raw team notes into the lessons log. Here's what we wrote down: 1) Registration was a total disaster, Priya was overwhelmed, the queue went out the door and the first talk started 10 minutes late - Priya grabbed two floor volunteers at 9:15 to clear it. We need better volunteers next year. 2) The AV guy kept screwing up mic handoffs in track B all afternoon. 3) The gluten-free lunch count was wrong; we flagged it and catering fixed it by 1pm. 4) Rain flooded the sponsor tent mid-morning and there was nothing anyone could do. Please turn these into our lessons-learned log and run a proper root-cause analysis on each one so we really understand them.",
"expected_output": "A dated log where each finding becomes a three-part entry (what happened, what was done in the moment, what changes next edition) written about conditions and systems rather than Priya or the AV operator, with named owners and dates, categories that route each finding, an accepted empty middle part for the rain, and root-cause escalation refused for all or nearly all entries.",
"files": [],
"expectations": [
"Writes each finding as a three-part entry: what happened, what was done in the moment, what changes next edition",
"Registration entry describes the structural condition (e.g. one staffed position against the arrival curve) rather than Priya being overwhelmed",
"Replaces evaluative adjectives like 'disaster' with observable facts such as queue reach and the 10-minute late start",
"Middle part of the registration entry preserves the improvised response (two volunteers pulled off floor duty at 9:15) so next edition can judge whether it worked",
"Rewrites 'we need better volunteers' into a concrete mechanism (e.g. sizing the desk against the arrival curve, a named float role) with a named owner and a due date",
"AV finding names the handoff process or briefing/checks, not the operator as a person",
"Rain/tent entry keeps an explicitly empty middle part ('nothing could be done during the event') instead of inventing an in-the-moment response",
"Declines to run root-cause or 5-Whys analysis on every entry, keeping entries deliberately shallow",
"If any deeper analysis is allowed, it is capped at one or two findings and gated on recurrence, structural cost, and the obvious fix being symptomatic",
"Sorts entries into gap categories such as nobody-owned-it, known-risk-no-treatment, first-time failure, or checklist miss",
"Routes the rain finding to the risk register as a new unscored risk category rather than proposing a tent fix as the whole answer",
"Uses the ownership/staffing category to route the registration finding toward a team-structure fix",
"Every entry describes gaps and systems, never a person, and the log is dated"
]
},
{
"id": 3,
"prompt": "Cascade DevDays is a 600-person conference in Portland; our debrief is Thursday. I have our risk register (12 scored risks), the planned budget, and the run of show in front of me. What happened: our keynote speaker cancelled the night before - that was risk #3 and the backup speaker list worked; the venue wifi died for two hours, which was never on the register; catering came in $6,800 over plan, AV came in $1,200 under, and sponsorship sold $4,000 below plan. Track A ran 25 minutes long all afternoon because transitions ate time. We never collected an attendee survey this year. In the debrief I want to re-score the whole risk register, set next year's catering budget, and rewrite the run of show so every transition gets 10 minutes. Can you prep all that for Thursday?",
"expected_output": "A debrief prep that refuses to re-score the register, re-budget, or rewrite the cue sheet, and instead produces four reconciliation handbacks: risks in three buckets, a variance table ordered by absolute size with one-sentence causes, run-of-show divergences as observations, and the missing attendee-feedback input named and skipped.",
"files": [],
"expectations": [
"Declines to re-score the risk register inside the debrief and hands back a reconciliation to the risk-management owner instead",
"Risk handback uses three buckets: fired with treatment held, fired with treatment failed, and fired but unscored",
"Places the keynote cancellation in the fired-and-treatment-held bucket since risk #3's backup list worked",
"Places the two-hour wifi outage in the fired-and-unscored bucket and frames it as a new risk category, not a fix",
"Identifies the unscored bucket as the most valuable output of the risk check",
"Budget check is actual-versus-planned variance ordered by largest absolute variance first: catering $6,800, then sponsorship $4,000, then AV $1,200",
"Attaches a one-sentence cause per material variance drawn from price move, volume miss, unplanned line, or estimate that was always wrong",
"Declines to set next year's catering number; the variance table is handed to the budget owner without proposed next-edition figures",
"Run-of-show output is a list of divergences as observations (Track A 25 minutes long, transitions eating time), not a rewritten cue sheet with 10-minute transitions",
"States that revising the cue sheet belongs to the run-of-show owner, not the debrief",
"Names the missing attendee feedback summary as a reconciliation that cannot be run, and skips it rather than reconstructing participant sentiment from memory",
"Does not propose surveying or contacting attendees now to fill the gap",
"Each reconciliation is routed to its owning sibling process, separate from the team's own dated lessons log"
]
},
{
"id": 4,
"prompt": "OrbitJS Mini-Conf just finished its fourth annual edition two weeks ago. My co-organizer wants the debrief document to open with charts comparing ticket sales, sponsor revenue and attendee satisfaction against editions two and three, so we can finally see the trend. One problem: we never wrote goals down this year - back in January we vaguely talked about 250 attendees and breaking even. We ended at 218 and lost about 900 euros. And we have no satisfaction number at all, we didn't measure anything. How should the debrief handle all of this?",
"expected_output": "A debrief scoped to this single edition's dated log, refusing the cross-edition trend charts, reviewing the reconstructed January goals with an explicit 'reconstructed, not measured' label, recording satisfaction as unmeasurable as a finding in itself, and keeping the goals verdict internal.",
"files": [],
"expectations": [
"Declines to build the cross-edition trend comparison inside the debrief and scopes the output to one edition's dated log",
"States that aggregating across editions belongs to a separate continuous-improvement process which receives this log",
"Reviews against the reconstructed January goals (250 attendees, break even) but explicitly labels the goals section reconstructed, not measured",
"Marks satisfaction as unmeasurable and treats the fact nobody instrumented it as a finding in its own right",
"Records attendance 218 against 250 and the roughly 900 euro loss as missed against the reconstructed goals",
"Keeps the goals verdict strictly internal: a signal about this edition's own targets, never a go/no-go on whether the event should continue",
"Routes any demand-relevant signal (attendance shortfall, financial miss) to the market-fit owner as a signal, not a conclusion",
"Records the two-week gap between doors closing and the debrief as a signal to note, not a target to hit",
"States zero orphan entries as the single binary pass threshold for the log",
"Proposes instrumenting satisfaction (or writing goals down) for next edition as an action item carrying a named owner and a due date",
"Checks whether edition three's action items were actually done as a carry-through input, while leaving the trend claim to the continuous-improvement process"
]
},
{
"id": 5,
"prompt": "During the KernelCraft Days debrief last night, our ops lead Tomás - a volunteer, though two of us organizers are paid staff at the sponsoring company - said flat out that he's done: he ran registration, volunteer coordination AND the sponsor desk this year with no backup and he's burnt out. My co-organizer wants two things: (a) a section in our public retrospective post honestly saying 'we overloaded Tomás and he nearly quit', to show accountability, and (b) an agenda item at next year's debrief to figure out how to redistribute his workload. She also thinks Tomás simply took on too much and should have said no earlier. How do we handle this?",
"expected_output": "The finding restated structurally (one person held three roles with no backup), routed to the team-structure owner now with an owned, dated entry rather than parked for next year, kept out of the public post by name, with the mixed-team blameless frame delivered by the reporting-line holder.",
"files": [],
"expectations": [
"Rejects the framing that Tomás took on too much or should have said no, calling that a personal-failing framing that ends the conversation",
"Restates the finding structurally: one person held three roles with no backup",
"Routes the workload redesign to the team-structure owner rather than solving the redistribution inside the debrief",
"States the debrief surfaces and routes team-health findings but does not redesign the team",
"Advises against publishing the finding with Tomás named; personnel-sensitive findings remove the public options entirely rather than just ranking them lower",
"Notes that a criticised volunteer simply stops volunteering, and that this loss is invisible in the log",
"References precedent that events historically published this kind of self-assessment only at shutdown (e.g. JSConf EU's closing statement or !!Con's burnout statement) and that the debrief exists to surface it years earlier",
"On a mixed volunteer/staffed team, the blameless frame must be stated most explicitly and delivered by whoever holds the reporting line, because from anyone else it does not bind",
"Notes that a volunteer sharing the room with paid staff or their day-job manager changes what the volunteer will say about workload",
"Writes the finding into the log now as a three-part entry with a named owner and a due date, instead of deferring it to next year's debrief agenda",
"Does not assign the workload-redistribution action item to Tomás himself",
"States that nothing said in the room becomes a performance judgment and only agreed written findings leave it"
]
},
{
"id": 6,
"prompt": "ForgePoint Conf (900 attendees, Berlin) ended last week. Two things happened very publicly: a speaker was removed mid-talk after a code of conduct violation - half the audience saw it and it's all over social media - and our badge printing collapsed for the first hour of day one. Now the team is split on what to publish. Our community manager wants a full transparency report with the incident details, our sponsor lead wants to publish nothing and let it blow over, and I just want the usual recap with photos. We also have an internal finding that tears into our badge vendor pretty harshly. What should we publish, and who gets to decide?",
"expected_output": "A ranked publication decision: silence rejected because the incident was visible, the transparency report gated on the code-of-conduct pipeline's anonymisation sign-off and its irreversibility named, the vendor-blaming finding kept out of or rewritten for the public post, and the decision made by the team in the room while findings are fresh.",
"files": [],
"expectations": [
"Frames the choice as a ranked menu of postures (nothing published, recap only, recap plus retrospective, plus transparency report) rather than a binary publish-or-not",
"Rejects publishing nothing given the incident was publicly visible, because silence would read as a cover-up - the stated condition that promotes the transparency report",
"Gates the transparency report on the code-of-conduct pipeline's own sign-off on anonymisation, and on the reports actually having been resolved",
"States that a published incident description cannot be unpublished",
"Specifies the transparency report as an anonymised account of reports and how each was handled, with no identifying detail about the speaker",
"Names recap plus retrospective as the default posture, or anchors it to the published recap-plus-retrospective precedent shape",
"Notes the retrospective's marginal drafting cost is low because findings already exist in three-part form",
"Flags the harsh badge-vendor finding: publicly naming a supplier can collide with non-disparagement terms and will reach a supplier the event may want next year, so it is rewritten or kept internal",
"The publication decision is made by the team, in the room, while findings are fresh - not taken away as one person's homework",
"Distinguishes the exposure each rung carries (photo consent for a recap, contractual for a retrospective, code-of-conduct sign-off for a transparency report) from mere drafting effort",
"Cites recap-level publishing as endorsed practice (results blogging described as optional but strongly recommended)",
"Allows the badge-printing failure itself to appear in the public retrospective as what went wrong plus what changes, since it is operational rather than personnel- or incident-sensitive"
]
},
{
"id": 7,
"prompt": "I'm facilitating the debrief for Solder & Code Festival (two-day hardware conference, 11 named roles, mostly volunteers plus Ingrid, our paid event manager) next Wednesday - we have 90 minutes. My plan: kick off with a quick dot-vote on the top 3 things that went wrong, spend an hour fixing those three, then wrap with any positives if there's time left. Two of the track leads already disagree about whether Saturday's workshop-room chaos was a check-in problem or a scheduling problem, so I figured I'd settle that debate first thing to clear the air. Oh, and our volunteer lead can't make Wednesday at all. Can you tighten this agenda for me?",
"expected_output": "A rebuilt agenda: blameless frame first and spoken by Ingrid, chronological timeline reconstruction from artifacts before any judgment, the workshop-room dispute marked disputed rather than settled, a dedicated what-went-well pass before what-went-poorly, reconciliations, an explicit team-health slot, owners-and-dates, publication decided in the room, and the absent volunteer lead's written input collected beforehand.",
"files": [],
"expectations": [
"Rejects opening with a vote on what went wrong; the session opens with the blameless frame stated out loud",
"On this mixed volunteer/staffed team, Ingrid as the reporting-line holder delivers the frame herself",
"Timeline reconstruction of the edition comes before any analysis, judgment, or fixing",
"Timeline is built from artifacts first (run of show, comms channel history, ticketing, photo timestamps) with memory only filling gaps",
"The workshop-room disagreement is recorded as disputed rather than settled first thing, and the dispute itself is treated as a finding that nobody knew what was happening at that moment",
"What-went-well runs as its own explicit pass before what-went-poorly, not as leftover time at the end",
"Justifies the well-first ordering by the risk that an unnamed working practice gets quietly dropped next edition",
"Agenda includes a reconciliation segment checking what happened against the documents that already exist (risk register, budget, run of show, pre-set goals)",
"Team health appears as an explicit agenda item rather than being left to whoever is brave enough to raise it",
"Agenda ends with an owners-and-dates segment where every entry gets a named person and a date or an explicit no-action",
"Publication posture is decided in the session by the team, not taken away afterwards",
"The absent volunteer lead submits written input beforehand, or their absence is named as a coverage gap - part of the event only they saw",
"Recommends a written well/poorly pre-read from every named role so the session discusses rather than collects, preventing the first speaker from anchoring the room"
]
},
{
"id": 8,
"prompt": "BrewCity JS Conf runs every October. Last year's debrief produced 15 action items in a doc - 'improve speaker AV checks', 'start sponsor outreach earlier', that kind of thing. The owner column mostly says 'team' and the deadline column says 'before next year'. Twelve months on we've completed exactly zero of them and we repeated at least three of the same mistakes this edition. Planning for next October opens in three weeks. My co-organizer's fix is to buy a project-management tool and run monthly review meetings all year. What actually went wrong, and what should we do differently this time?",
"expected_output": "A diagnosis of orphan action items (owner 'team', date 'before next year' tracked by nothing), the repeated mistakes tagged as incomplete fixes from last edition, a default of named owner-and-date per entry plus carry-over into the planning document opening in three weeks, and the year-round tool-plus-meetings idea pushed back on as a standing job.",
"files": [],
"expectations": [
"Diagnoses the core failure as orphan action items: an owner of 'team' and a deadline of 'before next year' are tracked by nothing",
"Requires each entry to carry one named person and a concrete date, or an explicit 'no action, because'",
"Tags the three repeated mistakes as incomplete fixes from last edition and identifies that category as the most valuable one, only existing from the second edition onward",
"Recommends the default combination: owner-and-date on every entry plus carrying open items over into next edition's plan",
"Open items are written into next edition's work-back plan as real tasks handed to the planning process, not left as log lines",
"Uses the three-week planning start to promote the carry-over hard: the plan opens now, so items go in the same week",
"Pushes back on the tool-plus-monthly-meetings proposal as the highest-effort option: a standing job rather than an appointment, promoted only when a year-round tracker already exists or findings must resolve between editions",
"Positions a mid-cycle check-in as one dated calendar entry reserved for short-fuse items (vendor conversation, refund, deposit), not a recurring meeting series",
"Applies the binary zero-orphan check: re-read the log line by line and either assign each entry or close it explicitly",
"Records the 0-of-15 carry-through rate as an input while leaving the trend across editions to the continuous-improvement process",
"States that a log full of unowned entries is meeting notes, not a lessons-learned log",
"Contrasts costs when steering the choice: carry-over and check-in cost roughly a calendar entry and under half an hour, versus the tracker as ongoing maintenance"
]
}
],
"trigger_queries": [
{ "query": "Our conference wrapped on Sunday - how do we run the post-mortem and who should be in the room?", "should_trigger": true },
{ "query": "design the post-event attendee survey for our conference", "should_trigger": false },
{ "query": "run a retrospective for our hackathon that ended yesterday", "should_trigger": true },
{ "query": "what questions should we ask attendees in the feedback form", "should_trigger": false },
{ "query": "we need a lessons-learned session for the organizing team after DevFest", "should_trigger": true },
{ "query": "how do we get more responses on our post-event speaker survey", "should_trigger": false },
{ "query": "post-event debrief agenda for my meetup team", "should_trigger": true },
{ "query": "compare attendance and satisfaction across our last three editions", "should_trigger": false },
{ "query": "should we publish what went wrong at our conference publicly or keep it internal?", "should_trigger": true },
{ "query": "trend our sponsor revenue over the past five years of the conference", "should_trigger": false },
{ "query": "nothing really broke this year - is a debrief still worth an evening?", "should_trigger": true },
{ "query": "which problems keep recurring across every edition of our meetup series", "should_trigger": false },
{ "query": "how do I turn our team's own notes after the event into something next year's edition actually uses", "should_trigger": true },
{ "query": "build a year-over-year improvement dashboard for our event series", "should_trigger": false },
{ "query": "who needs to be in the room for our event post-mortem", "should_trigger": true },
{ "query": "build a risk register for next year's conference", "should_trigger": false },
{ "query": "our volunteer team is exhausted - how do we review this edition without burning them out further", "should_trigger": true },
{ "query": "score likelihood and impact for a venue cancellation risk", "should_trigger": false },
{ "query": "one of our organizers said they're completely burnt out during the review - what do we do with that", "should_trigger": true },
{ "query": "what treatments should we plan for our top event risks next year", "should_trigger": false },
{ "query": "last year's debrief produced fifteen lessons and we did none of them - what went wrong with the process", "should_trigger": true },
{ "query": "draft next edition's conference budget", "should_trigger": false },
{ "query": "help me write up what went well and what went poorly for the organizing team", "should_trigger": true },
{ "query": "model next year's P&L for our hackathon", "should_trigger": false },
{ "query": "we want a blameless retro for the conference crew", "should_trigger": true },
{ "query": "help me negotiate the venue contract for next year's event", "should_trigger": false },
{ "query": "how soon after the event should the team retro happen", "should_trigger": true },
{ "query": "write the minute-by-minute cue sheet for event day", "should_trigger": false },
{ "query": "compare what actually happened on the day against our run of show and write up the differences", "should_trigger": true },
{ "query": "design the escalation chain for the live show", "should_trigger": false },
{ "query": "capture the catering budget overrun in our post-event review", "should_trigger": true },
{ "query": "restructure our volunteer team roles for next year", "should_trigger": false },
{ "query": "check which risks from our register actually fired during the event", "should_trigger": true },
{ "query": "how many volunteers do we need per track next edition", "should_trigger": false },
{ "query": "template for lessons-learned entries with owners and due dates", "should_trigger": true },
{ "query": "is there still demand for our conference or should we retire it", "should_trigger": false },
{ "query": "the event's over and everyone wants to move on - how do I get the team to reflect before we lose the details", "should_trigger": true },
{ "query": "build the work-back plan for next year's edition", "should_trigger": false },
{ "query": "we just finished our first hackathon, what should we write down before the team scatters", "should_trigger": true },
{ "query": "write a code of conduct for our conference", "should_trigger": false },
{ "query": "should our conference publish a transparency report about the code of conduct incident", "should_trigger": true },
{ "query": "set up the incident response process for CoC reports during the event", "should_trigger": false },
{ "query": "how do we decide between a public recap and keeping our findings internal", "should_trigger": true },
{ "query": "turn this year's conference talks into blog posts", "should_trigger": false },
{ "query": "structure a 90-minute wrap-up meeting for the organizing committee", "should_trigger": true },
{ "query": "when should we publish the talk recordings from our conference", "should_trigger": false },
{ "query": "the team keeps blaming one person for the registration mess in our review - how do I keep it constructive", "should_trigger": true },
{ "query": "should we run a roadshow or a single-city user conference next year", "should_trigger": false },
{ "query": "how do I reconstruct the event timeline for our review when memories already disagree", "should_trigger": true },
{ "query": "write a postmortem for last night's production outage", "should_trigger": false },
{ "query": "everyone remembers the day differently - how do we settle what actually happened before we judge it", "should_trigger": true },
{ "query": "run a blameless postmortem for our API incident", "should_trigger": false },
{ "query": "what do we do with action items nobody owns after the retro", "should_trigger": true },
{ "query": "SEV1 incident retrospective template for my SRE team", "should_trigger": false },
{ "query": "post-mortem for a meetup that had zero incidents", "should_trigger": true },
{ "query": "facilitate our sprint retrospective next Tuesday", "should_trigger": false },
{ "query": "the sponsor booth setup was chaos - should the debrief fix the floor plan or just log it", "should_trigger": true },
{ "query": "retro format ideas for my scrum team", "should_trigger": false },
{ "query": "write the retro doc for this year's edition so next year's team inherits it", "should_trigger": true },
{ "query": "run a retrospective on our Q3 product launch", "should_trigger": false },
{ "query": "we're handing the conference to a new organizing team - what should this year's review look like", "should_trigger": true },
{ "query": "marketing campaign post-mortem for our spring promo", "should_trigger": false },
{ "query": "how deep should we go on each finding in the event review - do we 5-whys everything?", "should_trigger": true },
{ "query": "put together the post-event report we owe our sponsors", "should_trigger": false },
{ "query": "did we hit the goals we set for this edition - how do we review that honestly", "should_trigger": true },
{ "query": "write thank-you emails to send attendees after the conference", "should_trigger": false },
{ "query": "review this edition against the goals we set back in January", "should_trigger": true },
{ "query": "plan the email sequence announcing next year's dates", "should_trigger": false },
{ "query": "our event went badly and I need a proper internal post-mortem that doesn't become a blame session", "should_trigger": true },
{ "query": "how do we reduce no-shows at the next meetup", "should_trigger": false },
{ "query": "attendee survey results are in - how do we combine them with our own team notes for the wrap-up", "should_trigger": true },
{ "query": "we're planning our first conference edition, where do we start", "should_trigger": false },
{ "query": "it's the final edition of our conference - do we still do a retrospective and publish anything", "should_trigger": true },
{ "query": "pick the date for next year's conference", "should_trigger": false },
{ "query": "how do I log 'we should fix this next year' items so they actually happen", "should_trigger": true },
{ "query": "design the CFP for next year's edition", "should_trigger": false },
{ "query": "quick debrief format for a two-person organizing team", "should_trigger": true },
{ "query": "how should we price sponsor packages for next year", "should_trigger": false },
{ "query": "what should the organizing team measure about its own post-event review", "should_trigger": true },
{ "query": "write the sponsorship prospectus for the next edition", "should_trigger": false },
{ "query": "the venue messed up lunch - how do we write that up in the lessons log without torching the relationship", "should_trigger": true },
{ "query": "improve the attendee experience at our next conference", "should_trigger": false },
{ "query": "our conference retro keeps turning into a performance review of the ops lead", "should_trigger": true },
{ "query": "what session formats should we use next year", "should_trigger": false },
{ "query": "what leaves the debrief room and which team gets which output", "should_trigger": true },
{ "query": "help me plan the after-party and social program", "should_trigger": false },
{ "query": "we skipped the retro two years running - convince my co-organizers it's worth an evening this time", "should_trigger": true },
{ "query": "figure out why ticket sales dropped this year and fix our marketing", "should_trigger": false }
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |