What problem does it solve? Recurring technical events repeat the same failures year after year because lessons live in scattered debrief docs, organizer memory, or logs nobody re-reads. This Skill turns several editions of debrief logs into defensible trends, deliberate changes, and a persisted learning log that survives team turnover. ## Core Features & Use Cases - Signal gate and theme grouping: Files each debrief entry through a current/reproducible/generalizing gate, clusters differently-worded findings into themes, and counts recurrence by edition (two occurrences = candidate, three = pattern). - Persisted learning log with audit: Chooses a persistence rung (appended document to structured entry record), then audits entries as Keep, Update, Consolidate, Replace, or Delete so the log never grows unexamined. - Deliberate changes and routing: Writes each change with evidence and an observable check, then routes demand signals to market-fit, scale questions to growth-strategy, vendor verdicts to vendor-sourcing, and structural recurrences to team-structure. - Use Case: After four editions of a conference where check-in broke every year, group the differently-worded findings into one check-in theme at 3 of 4 editions, propose one deliberate change with a measurable queue-length check, and hand it to the planning-timeline owner. ## Quick Start Ask the assistant to compare the debrief logs from your last three event editions and identify which recurring problems are real patterns worth changing next year.
