rpg-session-recap

RPG Session Recap (Pathfinder 2e kit — the return edge)

What this skill is for

Turn the GM's account of a just-played session into reconciled vault state — the one move the gamemaster kit has never had. Every other skill in the kit prepares or runs a session; this one closes it out. It reads what the GM says happened, connects every name to the vault's canon, proposes the concrete state changes that follow, and — where the account and the vault disagree — stops and asks the GM which path to take instead of guessing.

This is the return edge of the session cycle: party-forge → front-tracker → session-prep → encounter/embate-builder → run-sheet → [play] → rpg-session-recap → front-tracker → session-prep → …. Without it the loop is one-directional — the GM re-feeds front-tracker from memory, quest.status never flips, and evento/clue reveals are never captured. This skill makes the vault a living record instead of a forward-only pipeline.

The deliverable is two things: a GM-facing recap document (the session's beats, in prose) and a change set — the concrete, reviewable list of vault mutations this session produces, with any divergence flagged and adjudicated before anything is written.

The core idea — reconcile, don't just record

A recap that only transcribes what happened is a diary entry. The value here is reconciliation: checking the account against what the vault already believes to be true, and treating every mismatch as a decision point, not an error to paper over.

Three things drive every decision here:

1. The account is the session's truth; the vault is prior state; the bible is canon. When they agree, reconciliation is mechanical — update and move on. When they don't, that's the interesting case, and it belongs to the GM, not to a silent overwrite.
2. Every entity must resolve by exact name. A name in the account that doesn't match a vault note isn't a typo to guess past — it's either an existing entity under a different name, a new node that needs a handoff, or a fact worth pausing on.
3. Nothing gets written until the GM has seen the batch. Unambiguous updates are proposed together for one approval; genuine conflicts are adjudicated one at a time, with 2–4 concrete paths offered — never a bare "this doesn't match, what do I do?"