# ⚙️ Mechanics Exploration - Workflow Instructions

## Overview

This workflow guides you through a deep dive into your game's mechanics, core loop, and systems design.

**Time:** 45-90 minutes  
**Difficulty:** Intermediate  
**Output:** `mechanics-exploration.md`

---

## Step 1: Core Loop Definition

The core loop is what players DO repeatedly. It must be inherently fun.

### Loop Formula
```
[ACTION] → [FEEDBACK] → [REWARD] → [DECISION] → repeat
```

### Questions to Answer
1. What's the PRIMARY action? (one verb)
2. What's the immediate feedback?
3. What's the reward for success?
4. What decision leads to the next loop?
5. Why do players WANT to repeat?

---

## Step 2: Mechanic Inventory

List all the mechanics your game might have:

### Core Mechanics (Must Have)
- [Mechanic 1]
- [Mechanic 2]

### Supporting Mechanics (Should Have)
- [Mechanic 3]
- [Mechanic 4]

### Nice-to-Have Mechanics
- [Mechanic 5]

For each mechanic:
- What does it add to the experience?
- How does it interact with other mechanics?
- Reference games that do it well

---

## Step 3: Systems Mapping

How do your systems connect?

### Core Systems
- Player abilities/actions
- Challenge/opposition
- Win/loss conditions

### Support Systems
- Progression
- Economy
- Inventory

### Meta Systems
- Save/load
- Achievements
- Settings

**Map the interactions:** Does System A affect System B?

---

## Step 4: Depth Analysis

Goal: High depth, low complexity

### Depth Sources
✅ Mechanics that interact
✅ Trade-offs without "best" choices
✅ Multiple valid strategies
✅ Situational decisions
✅ Delayed consequences

### Complexity Red Flags
⚠️ Too many resources
⚠️ Rules with exceptions
⚠️ Non-interacting systems
⚠️ Information overload

---

## Step 5: Game Feel Considerations

How should actions FEEL?

### Feel Components
- Input responsiveness
- Visual feedback (screen shake, particles)
- Audio feedback
- Physics/weight

### Reference Games
What games have the feel you want? Why?

---

## Step 6: Prototype Priorities

What should be built first to validate fun?

### Minimum Playable Prototype
1. [Core action works]
2. [Basic feedback exists]
3. [One complete loop]

### What Can Wait
- Polish
- Content variety
- Meta systems

---

## Output: mechanics-exploration.md

The final document includes:
- Core Loop Design
- Mechanic Inventory
- Systems Map
- Depth Analysis
- Feel Direction
- Prototype Plan

Saved to: `_gdks-output/01-ideation/mechanics-exploration.md`

---

## Next Steps

After mechanics exploration:
1. **Synthesis** → `@ideation-coordinator` with `*synthesize`
2. **Design Team** → `@game-design-director` with `*create-gdd`

**Ready? Let's explore your mechanics!** ⚙️