Run an event debrief that changes the next event — what the numbers say, what actually went wrong versus what felt stressful, and the specific changes carried into the next brief. Use when asked to run a post-event debrief, write an event wrap report, review how an event went, or capture lessons learned after a conference, launch, or wedding. Produces the outcome scorecard against the original objectives, the timeline of what actually happened, the root causes separated from symptoms, supplier performance, and the changes written into the next event's brief.
“Run a debrief for last week's conference”“Write an event wrap report for the client”“How do I stop the same problems happening at every event?”“Capture lessons learned from our launch event”“What should we change for next year's gala?”
What to give it
▸The original objectives — what this event was supposed to achieve, from the brief
▸The numbers — attendance versus target, budget versus out-turn, and any measured outcomes such as leads, funds raised, or satisfaction
▸What happened — the actual timeline, incidents, and deviations from plan
▸Feedback — attendee, client, staff and supplier, and how it was gathered
▸The team's account — what each person found hard, gathered before the group discussion so it is not shaped by the loudest voice
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Objectives and numbers are reviewed before any discussion of how it felt
✓The actual timeline is reconstructed against the plan
✓Each problem is classified as felt-bad or was-bad
✓Root causes point at earlier decisions, not at the moment of failure
✓Individual accounts were collected before the group session
✓Supplier notes are specific enough to be useful at next procurement
✓What worked is recorded, not only what failed
✓Fixes are written as instructions into the next brief, with owners
⚠️ What it refuses to do
**Debriefing on feelings alone.** The stressful and the harmful are not the same set.
**Fixing symptoms.** The AV failure was a March procurement decision; changing the cable supplier fixes nothing.
**Group discussion first.** Produces one story, usually the most confident person's.
**'Supplier was fine.'** Useless as evidence a year later.
**Recording only failures.** What worked is how you keep it working.
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp