Menu

Individual skill

post-event-debrief

0upvotes

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.

plugins/pm-events/skills/post-event-debrief/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Post-Event Debrief

Most event debriefs produce a feelings-based list nobody reads before the next event, and the same three problems recur annually. This separates what went wrong from what merely felt stressful, traces each problem to the decision that caused it — usually made weeks earlier — and writes the fixes into the next brief rather than into a document that gets filed.

## What This Skill Produces

- **The outcome scorecard** — performance against the objectives set before the event, not against how it felt
- **The actual timeline** — what really happened versus the run of show, with the slippage visible
- **Root causes** — each problem traced back to the decision or omission that produced it
- **Supplier performance** — a record specific enough to be useful at the next procurement
- **The budget out-turn** — final versus budget, with the variances explained
- **Changes into the next brief** — the fixes, written as instructions to the next event rather than observations about this one

## Required Inputs
Back to top