“游戏BOSS设计”

Quest/Mission Design Template

Designs quests with player motivation, fail states, and systemic interactions — avoids FedEx-quest filler.

Hook: how the player naturally encounters it (world event/overheard/board/

Structure: objective beats with at least TWO valid approaches (combat/stealth/

Script: key NPC dialogue in voice (10-20 lines), including a lie/misdirection

Rewards: exp/items mapped to expected level, world-state change (visible

Data: quest ID, prerequisite flags, fail/recovery states, edge cases (NPC

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

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

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

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