Game planning

Record existing genre, target device, input roles and selected modes before expansion. Keep the slice small enough to validate; do not add combat, locomotion, loot or progression merely to satisfy an action-game template.

Slice contract

Publish:

• stable slice_id and slice_revision
• pillars and explicit scope exclusions
• target/device/input context
• core challenge or decision
• start and end conditions
• failure/retry or explicit no-failure policy
• dependent skill modes/versions
• acceptance evidence and untested remainder
• next milestone and exit criteria

The player understands the goal, completes one core challenge or decision, perceives its consequence, and knows what to do next. Combat is one possible loop; noncombat games are equally valid.