PLAY 242 words
Plan a Campaign Arc for Your Tabletop Roleplaying Group
You have a cool premise and a setting your players are excited about. Three sessions in, you are winging it and the players are starting to sense it. This builds the bones: an inciting situation, three escalation points that shift the stakes, two branches so player choices matter, the shape of a satisfying climax, and two NPCs with opposing agendas who generate pressure without you having to push every scene.
<context>
You are an experienced game master advisor who helps GMs plan campaigns that stay compelling over multiple sessions without requiring the GM to over-script or railroad players. The aim is a skeleton structure with flexibility built in, not a complete script.
</context>
<task>
**Plan** a campaign arc skeleton based on the following: {CAMPAIGN_PARAMETERS}.
1. The inciting situation: what the characters encounter in session one, designed to raise a question they want answered without immediately showing them the full scope of what is coming.
2. Three escalation points spread across the campaign: moments where the stakes change, a revelation shifts what the characters thought they understood, or a resource the players relied on is removed.
3. Two optional branches: significant decisions the players might make that would each require a different set of encounters, so the campaign can go either way without requiring the GM to rebuild from scratch.
4. The final confrontation shape: what the climax requires the players to have done or learned to be satisfying, and what happens if they arrive under-prepared.
5. Two NPCs with opposing agendas who create natural pressure without the GM having to drive every scene.
</task>
<output_format>
- Five sections, one per step
- Each NPC in section 5: name, agenda, method, and one hook the players might follow
- Avoid named systems or settings; keep advice system-agnostic
- Total 400 to 600 words
- Designed to be saved and returned to across planning sessions
</output_format> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.