pressure-test

# Campaign Pressure Testing

## Purpose

Systematically challenge campaign content by adopting an adversarial player mindset. Identify weaknesses, plot holes, and failure points before players discover them.

## Pressure Test Process

### 1. Gather Context

Load the campaign and module being tested:

```
get_campaign_details()
get_module_details(module_id: module_id)
list_characters(character_type: "npc")

# Check for maps and token placements
list_maps(module_id: module_id)
get_map(map_id: map_id)

# Check campaign-level documents for world context
list_documents()  # omit module_id for campaign-level docs

# Check for orphaned NPCs (not assigned to any module)
list_characters(character_type: "npc")
# Flag any NPC without a module assignment or location
```

Read all relevant documents to understand the scenario.

### 2. Apply Pressure Test Categories

Work through each category, asking probing questions:

**Murder Hobo Test**
- What if players kill the quest giver immediately?
- What if they attack every NPC on sight?
- Are there consequences that don't dead-end the campaign?

**Skip Content Test**
- What if players ignore the hook entirely?
- Can they bypass the dungeon and go straight to the BBEG?
- What if they refuse the quest?

**Clever Solution Test**
- Can they solve this with a single spell (Fly, Teleport, Speak with Dead)?
- What if they befriend the villain?
- Can divination magic reveal too much too early?

**Resource Test**
- What if they're out of spell slots when they reach the boss?
- What if they have unlimited money to throw at the problem?
- What if they hire an army of mercenaries?

**Information Test**
- What happens if they miss the key clue?
- Are there backup ways to get critical information?
- What if they get information out of order?

**Social Test**
- What if they intimidate/charm their way past obstacles?
- Can high Persuasion trivialize the challenge?
- What if they take hostages?

### 3. Document Findings

For each issue found, catego