Break into epics with dependency graph (what art needs design locks, what code
Sprint-by-sprint backlog table: feature | owner | design lock date | asset
Capacity reality: account for {{holidays/sick/context-switch/support}}, leave
Risks register (probability × impact, owner, mitigation), playtest schedule
Recruitment: target players vs convenience testers, sample size per round
Observation: timing targets (time-to-first-verb, deaths per room, checkpoints
Cadence: rolling weekly tests, hypothesis per change, and how to avoid
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
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,
Deck outline for publisher/platform: slide list with the data each needs
Comfort and motion sickness
