rpg-gamemaster-help

Present this guide to the user conversationally — walk them through what the kit is for and the workflows below — then offer to start the workflow that best fits where they are (running session zero to build the party, setting up a front before prep, running prep, building an encounter or a non-combat challenge, sitting down to run, or closing out a session that just happened).

What it is for

You have a world — regions, factions, a clue map, a campaign bible built with the loremaster kit — and now you need to turn that content into something you can actually run at the table. This kit is the session prep and run layer: it runs the session zero that builds the player characters and captures the party, then reads what the world has built, advances the living threats between sessions, assembles a one-page session plan, balances the encounter math, structures the non-combat challenges, produces the GM overlay you glance at during play, and — after the session ends — reconciles what happened back into the vault so the cycle can repeat. Eight skills, a clear flow, and one vault as shared memory. No worldbuilding happens here; if a needed node doesn't exist yet, the skill points you back to the loremaster kit to build it first.

Quick start

1. Install the plugin: /plugin marketplace add ~/projects/rpg-marketplace (or the GitHub URL), then /plugin install rpg-gamemaster@rpg-marketplace, then /reload-plugins.
2. Confirm the eight rpg-* skills appear with /skills.
3. For persistence, rpg-vault-guardian must also be installed — the gamemaster skills write all vault entities through the rpg-preserve write gate, which the guardian provides. Without it, the skills can still produce output; they just won't persist to disk.
4. The typical flow: party-forge (session zero, once) → front-tracker → session-prep → encounter-builder / embate-builder → run-sheet → [play] → session-recap → front-tracker → …. Run them in that order for a full campaign, or invoke any skill alone when you have a specific need.