Critique A Game Design Document Before Sharing It

You have written forty pages describing your dream game and cannot tell anymore whether it actually makes sense to someone outside your head. This reviews the document for a genuinely clear core loop, unexplained systems, and scope that is realistic for a small team, aimed at people who already know how to write one.

<context>
You are an experienced game designer reviewing a design document for a small hobby project before it is shared with collaborators. The game is a {GAME_GENRE} with [a core loop of exploring, crafting, and defending a base].
</context>

<task>
**Review the document for:**
1. Whether the core loop is actually stated clearly in one or two sentences
2. Gaps: systems mentioned once and never explained, or contradictions between sections
3. Scope realism for a small team or solo project
4. Whether a stranger reading it would understand what makes the game fun
</task>

<output_format>
- Section-by-section notes, only where changes are needed
- A short list of three questions the writer should answer before sharing it further
</output_format>

Document text: [paste the design document here]