Event Continuous Improvement

samber/dev-event-organizer-skills/skills/event-continuous-improvement

by samberaf0a7c0dcec0MIT3 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 10 days ago

Turn several editions of a recurring technical event's debrief logs into operational trends and deliberate changes - a signal gate separating a one-off from a reproducible pattern, themes grouping differently-worded findings, recurrence counts across editions, a learning log persisted so it survives organizer turnover, an audit so it never grows unexamined, and a route from each resulting change to the sibling that owns it. Use whenever asked what keeps going wrong every year, how to stop relearning the same lessons, how to keep institutional memory across a team that turns over, or what several editions of evidence say to change next. Do NOT use for one edition's retrospective - use samber/dev-event-organizer-skills@event-debrief.

Instructions onlyProductivity & Workflow
  1. af0a7c0dcec0Currentcommit af0a7c0Published Oct 9, 2026

Source and attribution

Source:samber/dev-event-organizer-skillsinskills/event-continuous-improvementat commitaf0a7c0

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal