# Ideation Handoff Document

## Game: [Game Title]
## Handoff Date: [Date]
## Ideation Team Lead: Ivy (Ideation Coordinator)

---

## Executive Summary

[2-3 paragraph summary of the game concept, what makes it unique, and why it's ready for design]

---

## Vision Statement

```
[GAME TITLE] is a [GENRE] game for [PLATFORMS] targeting [AUDIENCE].

Players experience the fantasy of [CORE FANTASY] through [CORE MECHANICS].
The game stands out by [UNIQUE HOOK], differentiating from competitors
like [COMPETITOR 1] and [COMPETITOR 2].

The core experience is [EMOTION/FEELING], achieved through [KEY FEATURES].
Development scope is [SCOPE LEVEL] with an estimated timeline of [TIMELINE].
```

---

## Concept Summary

### The Hook
**What makes this game unique:**
[One clear sentence explaining the hook]

### The Fantasy
**What the player gets to be:**
[Description of the power fantasy/role]

### The Core Loop
**What the player does repeatedly:**
```
[Action] → [Feedback] → [Reward] → [Motivation] → [Repeat]
```

### Elevator Pitch
> "[30-second pitch for the game]"

---

## Validation Results

### Validation Scores
| Dimension | Score | Notes |
|-----------|-------|-------|
| Desirability | /10 | [Brief note] |
| Uniqueness | /10 | [Brief note] |
| Feasibility | /10 | [Brief note] |
| Marketability | /10 | [Brief note] |
| Team Passion | /10 | [Brief note] |
| **Overall** | **/10** | |

### Validation Status: ✅ APPROVED / ⚠️ CONDITIONAL / ❌ NOT APPROVED

---

## Market Position

### Target Audience
- **Primary:** [Description]
- **Secondary:** [Description]
- **Estimated Size:** [X players]

### Competitive Landscape
| Competitor | Their Strength | Our Differentiation |
|------------|----------------|---------------------|
| [Game 1] | [Strength] | [How we differ] |
| [Game 2] | [Strength] | [How we differ] |
| [Game 3] | [Strength] | [How we differ] |

### Positioning
**For** [target audience] **who want** [desire], **[Game Title] is a** [genre] **that** [key benefit]. **Unlike** [competitor], **we** [differentiator].

---

## Mechanics Overview

### Core Systems Required
1. **[System Name]** - [Brief description] - Priority: Critical
2. **[System Name]** - [Brief description] - Priority: Critical
3. **[System Name]** - [Brief description] - Priority: High

### Reference Games for Feel
1. [Game] - [What to reference]
2. [Game] - [What to reference]

### Prototype Priorities
1. [What to prototype first]
2. [What to prototype second]
3. [What to prototype third]

---

## Scope & Constraints

### Team Resources
- **Team Size:** [X people]
- **Key Roles:** [List available roles]
- **Experience Level:** [Description]

### Timeline
- **Target Completion:** [Date/Duration]
- **Milestone Targets:**
  - Prototype: [Date]
  - Vertical Slice: [Date]
  - Alpha: [Date]
  - Beta: [Date]
  - Release: [Date]

### Budget
- **Available Budget:** [$X]
- **Key Allocations:** [Where money will go]

### Scope Classification
- **Overall:** Small / Medium / Large
- **Content Amount:** [Description]
- **System Complexity:** [Description]

---

## Success Criteria

### Creative Success
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

### Commercial Success (if applicable)
- [ ] Sales target: [X copies]
- [ ] Revenue target: [$X]
- [ ] Review target: [X%]

### Personal/Team Success
- [ ] [Criterion 1]
- [ ] [Criterion 2]

---

## Known Risks

### High Priority
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk] | High | [Plan] |

### Medium Priority
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk] | Medium | [Plan] |

### Accepted Risks
| Risk | Reason Accepted |
|------|-----------------|
| [Risk] | [Reason] |

---

## Open Questions for Design Team

### Gameplay Questions
1. [Question]
2. [Question]

### Content Questions
1. [Question]
2. [Question]

### Technical Questions
1. [Question]
2. [Question]

---

## Recommendations for Design Team

### Priority Focus Areas
1. **[Area]:** [Why it's priority]
2. **[Area]:** [Why it's priority]
3. **[Area]:** [Why it's priority]

### Potential Challenges
1. **[Challenge]:** [Suggested approach]
2. **[Challenge]:** [Suggested approach]

### What NOT to Do
1. [Anti-recommendation with reason]
2. [Anti-recommendation with reason]

---

## Attached Documents

| Document | Location | Status |
|----------|----------|--------|
| Concept Brief | `_gdks-output/01-ideation/concept-brief.md` | ✅ Complete |
| Market Analysis | `_gdks-output/01-ideation/market-analysis.md` | ✅ Complete |
| Mechanics Exploration | `_gdks-output/01-ideation/mechanics-exploration.md` | ✅ Complete |

---

## Handoff Confirmation

### Ideation Team Sign-off
- **Sparky (Concept):** ✅ Approved
- **Marcus (Market):** ✅ Approved
- **Mira (Mechanics):** ✅ Approved
- **Ivy (Coordinator):** ✅ Approved

### Handoff Statement
```
The Ideation Team formally hands off the concept for [GAME TITLE] 
to the Design Team.

All ideation documents are complete and validated.
The concept is ready for Game Design Document creation.

Date: [Date]
```

---

## Next Steps

1. **Design Team Lead** (Diana) receives handoff
2. Run `*create-gdd` to begin Game Design Document
3. Schedule kickoff meeting if needed
4. Begin GDD with Core Gameplay section

---

## Quick Reference for Design Team

### Commands to Start
```
@game-design-director   # Load Diana
*create-gdd             # Start GDD creation
*systems-design         # Detail systems
```

### Key Files to Reference
- Hook & Fantasy → `concept-brief.md`
- Audience & Position → `market-analysis.md`
- Loops & Systems → `mechanics-exploration.md`

---

*Handoff prepared by Ivy, GD-KS Ideation Coordinator*
*Ideation Phase: COMPLETE*