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 |
references/field-precedent.md
View on GitHub# Field precedent
What published organizer guides and event recaps say about post-event review, and why the session mechanics elsewhere in this skill come from a different lineage.
## What organizer guides publish
- **Write the Docs Prague 2017** published a "Recap and Retrospective" combining the attendee survey with the team's own retrospective - "a few main points that we received, which also reflect our own retrospective results" - and a code-of-conduct transparency report. Write the Docs Day Australia followed the same pattern. Both are dated 2017. **Write the Docs's own subsequent editions did not repeat the pairing.** Its own site publishes a "thanks and recap" post after nearly every later edition (Prague 2018-2020, Portland 2018-2021, Australia 2018 and 2020, Vilnius 2019) - each still carrying the recap and the code-of-conduct transparency report, but the explicit retrospective section is gone. Prague 2018's post narrows the whole retrospective down to one soft line: "We also had some interesting feedback on some things we might improve for next time." The 2017 pairing stayed a one-off inside its own source, not just externally.
- **MLH's organizer guide** names a retrospective as one line on a post-event checklist, opened by three questions.
- **DevOpsDays' organizing guide** has one post-event review line, scoped to code-of-conduct incidents only: "After the event, review any CoC violations and assess how they were handled." Its separate survey line adds "blogging about the results is optional, but strongly recommended."
- **MLH's `Organizer-Resources/keeping-records.md`** names three things - when ("a 1-hour event reflection with your team a few days after the event"), who ("your team", then "next year's organizing team"), and what artifact (a reviewed document, kept in a shared folder) - plus three opening questions about attendee feedback, planning challenges, and useful resources.
- **The Kubernetes Contributor Summit's own organizing team publishes a dated `RETRO.md` after each edition**, in the open-source `kubernetes/community` repository, spanning five editions from 2018 through late 2019 (2018-05, 2018-12, 2019-05, 2019-06, 2019-11). Each follows this skill's own "what went well" / "what could be improved" split, with points attributed to named organizers, attendance figures, and unresolved items carried forward. This is a genuinely current, repeated (not one-off) post-2017 precedent for the retrospective half of a debrief - but it differs in kind from Write the Docs's artifact: it is raw team retrospective notes made public by an open-governance norm, not a polished external recap written for an attendee audience, and it carries no code-of-conduct transparency component.
- **The Summer Institutes in Computational Social Science (SICSS) publish an annual, structured post-mortem** covering every partner site, spanning 2018, 2020, 2021 and 2022 editions, stating up front that each entry covers "how the Institute was run, what each site thinks worked well, and what each site will do differently next time" - the same three-part shape this skill's own lessons-learned entries use, sourced independently of Write the Docs. SICSS sits adjacent to, rather than inside, developer conferences (a computational social science and data science research program), and its post-mortem is a multi-site comparative document rather than a single recap.
- **Peter-Paul Koch ("PPK"), organizer of Fronteers and CSS Day**, publishes a "Conference Organiser's Handbook" with a dedicated Evaluation section naming concrete debrief mechanics for a developer conference: hold it "at the end of your conference" the same day, call all organisers together as a group, and "go through the various stages of organising in order, ask everyone for their feedback, and make a list." The scope is explicitly bounded - "concentrate on things that went wrong just before or during the conference," since this "is not the time to make changes to the concept," which gets its own separate annual-planning meeting instead ([quirksmode.org](https://quirksmode.org/coh/conference.html)).
- **Howard Givner, writing for the PCMA Institute**, describes his own post-event debrief practice from running the event "Paint The Town Red": exchange topic lists with the client beforehand, the way HR departments share written performance reviews ahead of the review meeting, so neither side is ambushed in the room; then split the agenda into "Big Picture" (the event's goals and whether they were met) ahead of "Production Details," so the room doesn't spend as long dissecting a gift bag as it does on whether the event actually worked ([pcmainstitute.org](https://pcmainstitute.org/the-debrief-from-hell/)).
- **Bizzabo's own guide** adds a timing data point without new mechanics: a debrief "should happen as soon as possible after an event ends," while the experience is still fresh, framed as the meeting where "team leaders analyze the show's performance and compare results" ([bizzabo.com](https://www.bizzabo.com/blog/event-debrief-questions)).
None of these sources publishes a figure for how many debrief lessons actually get acted on. Quoting one from software engineering would present a borrowed number as domain practice, which is why SKILL.md § Measurement sets its own pass threshold instead.
## Why the session mechanics come from elsewhere
Organizer guides mostly say little to nothing about debrief format. One clear exception: PPK's handbook names when (immediately, same day), who (all organisers), and format (walk the stages of organizing in order, compile feedback into a list) - but nothing past that. It has no reconciliation against a risk register or budget, no three-part entry structure, no owner-and-date discipline on action items, and no blameless-frame script. The rest of the mechanics in SKILL.md - the rest of when to hold the debrief, who attends, how the log reaches the next plan - still come from the SRE incident-postmortem lineage, adapted to an asset that runs once a year rather than a service that breaks on a weekday.
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 |