# Debrief Table

> Run the organizing team's internal retrospective on one finished edition of a technical event, then write the dated
> lessons-learned log or the session agenda. Enter when the doors closed and the debrief is booked, the team and every
> named role, the documents that exist to reconcile against and the draft entries. Built on the SkillSafe skill
> @samber/event-debrief (samber/dev-event-organizer-skills, MIT).

https://debrief-table.skillsafe.ai/

## What is free
- The debrief timing: booked at all (every edition, never skipped), before next edition's planning starts, and downgraded past six weeks.
- Named-role coverage - who is in the room or gives written input, and who has no voice.
- Every entry checked: blame wording or a person named as the cause, burnout framed as a personal failing, orphans (no owner or no due date), three parts, "no action" without a reason, cross-edition trends, overdue items; team-health entries listed for routing; the what-went-well pass.
- The reconciliations possible against the feedback summary, risk register, planned budget, run of show and the goals set before the event.
- The depth (pre-read plus one session by default; per-track; multi-track written review for a handover), publication (recap plus retrospective by default; transparency report with sign-off; nothing for a private event) and tracking (owner and date plus plan carry-over; check-in; standing tracker) menus with their deletions.
- The session agenda scaled to the minutes booked, and the one pass threshold: zero orphan entries.
- Log CSV, Markdown and JSON exports.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (log or agenda), `edition`, `entries` and `facts`.
- `log` replies with `summary`, `frame`, `entries`, `routed`, `reconciliations`, `depth`, `publication`, `tracking`, `signals` and `caveats`; the page holds every entry's kind, owner, date and status, the routing, the document statuses and the menu picks to its own, and rejects a person named as a cause.
- `agenda` replies with `title`, `opening`, `prereads`, `segments`, `close` and `note`; the page holds the segments and minutes and the pre-read roles to its own.

## Links
- API tutorial: https://debrief-table.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-debrief