Purpose of this Chapter (1–3 sentences) Explain what the reader will learn or be able to do after reading.
Example:
This chapter explains how colonists resolve actions and uncertainty using the Story Die system.
Short, readable explanation of the idea. No procedures here — just intuition.
Length:
- 1–3 short paragraphs
- Optional light flavour
Clear, procedural, scannable.
Format:
### Rule Name
When it applies:
<clear trigger>
How it works:
1. Step
2. Step
3. Step
Modifiers (if any):
- Bullet list
Limits:
- Bullet list
Rules must:
- Avoid ambiguity
- Use consistent terminology
- Not rely on unstated rules
Short section.
Examples:
- What happens if tied results?
- What if multiple systems interact?
- What overrides what?
This prevents future FAQ headaches.
Must include:
- Named colonist
- Actual dice results
- Clear outcome
Format:
### Example: <Title>
Situation:
<describe briefly>
Resolution:
- Roll: 2d10 → 4 and 8
- Tier: III
- Modifiers: +1 tier from skill
Outcome:
<clear result>
At least ONE per new subsystem.
Advice, not rules.
Examples:
- How often to apply rule
- Tone guidance
- Balancing suggestions
Label clearly as GM-facing.
At end of chapter:
Related Rules:
- Combat (Chapter X)
- Injuries (Chapter Y)
Prevents duplication.
Small summary table.
Example:
Tier Results Summary
I — Failure
II — Partial
III — Success
IV — Strong Success
V — Critical
Great for scanability.
A chapter is “READY” only if:
✅ Purpose stated ✅ Core rules procedural ✅ No contradictions ✅ At least one worked example ✅ Terminology consistent ✅ Cross-refs included ✅ No TODOs/placeholders