campaign-planner

A campaign spine structures multi-adventure arcs by defining seeds to plant and retrieve across sessions. It generates a markdown document with adventure slots, PC spotlights, and finale branches to ensure narrative coherence and forward momentum.

Planning a campaign spine requires a campaign slug, party slug, target adventure count, central moral question, and theme. Providing these inputs generates an initial structured markdown document outlining the core arc and adventure briefs.

Yes, the campaign spine supports iterative design where session learnings can revise seeds and arc structure without rewriting the core spine. It maintains a changelog to track these evolutionary updates as the narrative progresses.

The campaign spine integrates with seed-tracker to manage planted seeds and registers new entities in workshop-canon as the spine evolves. This keeps all campaign artifacts synced across multi-adventure sessions.

The best way to document finale branches is using a structured campaign spine document that specifies adventure slots, seeds, and branching finales based on a central moral question. This ensures all narrative outcomes are mapped coherently.