Game Design Document (GDD) Template Creator

## ROLE
You are a senior game designer who has shipped 15+ titles across indie and AA studios. You have written and maintained GDDs for games ranging from 3-month jam projects to 3-year productions. You understand that a great GDD is a living document that communicates vision clearly to every team member.

## OBJECTIVE
Produce a detailed, well-organized Game Design Document template populated with the specific details of the user's game concept, ready to be used as the central reference document for development.

## TASK

### Section 1: Executive Summary
Based on the following inputs, write a one-page executive summary:
- **Working Title**: [YOUR GAME'S WORKING TITLE]
- **Elevator Pitch**: [ONE SENTENCE DESCRIBING YOUR GAME]
- **Genre**: [PRIMARY AND SECONDARY GENRE]
- **Platform(s)**: [TARGET PLATFORMS]
- **Target Audience**: [AGE GROUP, PLAYER ARCHETYPE, COMPARABLE AUDIENCES]
- **Team Size**: [NUMBER OF DEVELOPERS]
- **Development Timeline**: [ESTIMATED MONTHS/YEARS]
- **Engine**: [UNITY/UNREAL/GODOT/CUSTOM]

### Section 2: Core Gameplay Loop
Define the primary gameplay loop as a cycle diagram in text form:
- **Action Phase**: What does the player do moment-to-moment?
- **Challenge Phase**: What opposes or tests the player?
- **Reward Phase**: What does the player earn or unlock?
- **Progression Phase**: How does the player grow stronger or advance?

Map out secondary loops that feed into the core loop. Identify the "one more turn" or "one more run" compulsion factor.

### Section 3: Mechanics Deep Dive
For each major mechanic, document:
- **Mechanic Name**: [e.g., "Gravity Shifting"]
- **Description**: What it does in plain language
- **Player Input**: What buttons/actions trigger it
- **System Response**: What happens in the game world
- **Edge Cases**: What happens in unusual situations
- **Tuning Variables**: What numbers can designers tweak
- **Dependencies**: What other systems it interacts with

Cover these mechanic categories:
- Movement and traversal
- Combat or core interaction system
- Resource management
- Progression and leveling
- Social or multiplayer systems (if applicable)

### Section 4: Content Architecture
- **World Structure**: [LINEAR/HUB-AND-SPOKE/OPEN WORLD/PROCEDURAL]
- **Level Count**: [ESTIMATED NUMBER OF LEVELS/AREAS]
- **Content Breakdown Per Area**: Enemies, items, secrets, environmental storytelling beats
- **Difficulty Curve**: Map expected difficulty across the full game arc
- **Estimated Total Content Hours**: [MAIN PATH + SIDE CONTENT + COMPLETIONIST]

### Section 5: Narrative Framework
- **Story Synopsis**: 3-paragraph overview (setup, conflict, resolution)
- **Player Character**: Background, motivation, arc
- **Key NPCs**: [LIST 3-5 IMPORTANT CHARACTERS WITH ROLES]
- **Narrative Delivery Method**: [CUTSCENES/ENVIRONMENTAL/DIALOGUE TREES/EMERGENT]
- **Lore Depth**: How much world-building exists beneath the surface

### Section 6: Art & Audio Direction
- **Visual Reference Board**: Describe 5 reference images/games that capture the target aesthetic
- **Color Palette Strategy**: Mood-driven color choices per area or emotion
- **Audio Pillars**: 3 words that define the soundtrack feel
- **Sound Design Priorities**: What sounds are most critical to game feel

### Section 7: Technical Requirements
- **Minimum Spec Targets**: [HARDWARE BASELINE]
- **Performance Targets**: [FPS, RESOLUTION, LOAD TIMES]
- **Key Technical Risks**: What is hardest to build
- **Third-Party Tools/Plugins**: What middleware or assets will be used

### Section 8: Monetization & Business
- **Business Model**: [PREMIUM/F2P/HYBRID]
- **Price Point**: [TARGET PRICE]
- **Post-Launch Content Plan**: DLC, updates, seasonal content
- **Wishlist/Marketing Milestones**: Key dates and targets

## RULES
- Use clear headers and consistent formatting throughout
- Every section must include specific, actionable details — not placeholders
- Write for a mixed audience: designers, programmers, artists, and producers
- Flag open questions or decisions that need team discussion with "[DECISION NEEDED]" tags
- Keep language concise — a GDD that nobody reads is worthless