“EN-01-Code-Generation-Prompts”

Production / Sprint Planning for Game Teams

Turns a milestone goal into a dependency-aware plan for art/design/engineering, with vertical-slice logic and risk spikes.

Milestone intent: what fun hypothesis or production risk this milestone kills

Capacity reality: account for {{holidays/sick/context-switch/support}}, leave

Risks register (probability × impact, owner, mitigation), playtest schedule

Playtest Plan & Qualitative Analysis

Runs useful playtests: recruitment, tasks, observation, and unbiased debrief interviews; converts footage into design changes.

Recruitment: target players vs convenience testers, sample size per round

Script: welcome/neutral framing (don't sell the game), warm-up, 3-5 task goals

Observation: timing targets (time-to-first-verb, deaths per room, checkpoints

Analysis: affinity-map observations into issues with severity/frequency

Cadence: rolling weekly tests, hypothesis per change, and how to avoid

Game Analytics / KPI Instrumentation Plan

Defines the events and funnels a game team actually needs — without drowning in data or violating privacy.

KPIs that drive decisions: D1/D7/D30 retention, session length/frequency,

Event schema: event name convention (noun_verb_past), required common fields

Funnel/heatmap tables: per-level (enters/retries/death-cause/loot/clear times),

Dashboards/alarms: live health dashboard, version-compare after patches,

Privacy/process: data retention, opt-out/child accounts, platform policy

Store Page / Pitch Deck / Trailer Brief

Marketing-ready positioning assets: hook hierarchy, trailer beat sheet, store screenshots with intent — written as a brief to marketing/art.

Positioning: target player statement ("for players who love X but want Y"),

Screenshot plan (7): order = fantasy hook, unique mechanic, wow moment,

Trailer brief (60-90s): beat sheet with seconds (cold-open hook in 0-5s,