What problem does it solve? After a conference, meetup, or hackathon ends, teams either skip reflection entirely or hold blame-heavy meetings whose lessons never reach next edition's plan. This Skill structures a blameless post-event debrief that produces a dated lessons-learned log with owned, dated action items. ## Core Features & Use Cases - Blameless session facilitation: Opens with an explicit blameless frame, reconstructs the timeline from artifacts before any judgment, and runs what-went-well and what-went-poorly as separate passes. - Four reconciliations: Checks what happened against the risk register, planned budget, run of show, and pre-set goals, handing each result back to the sibling process that owns it rather than re-diagnosing. - Lessons-learned log: Writes every finding as a three-part entry (what happened, what was done in the moment, what changes next edition) with a named owner and due date or an explicit no-action. - Publication posture decision: Guides the team through ranked options from publishing nothing to a full transparency report, with compliance exposure per rung. - Use Case: Your 400-person conference ended last week. Use this Skill to plan the 90-minute debrief agenda, turn raw team notes into a structured log, reconcile the catering overrun against the budget, and decide whether to publish a public retrospective. ## Quick Start Use the event-debrief skill to plan and run our organizing team's retrospective for the conference edition that just ended.
