Add ONE iconic Version 1 feature — the "wow" moment. Only one.

Discussion Question: Notice how Nintendo introduces ONE new mechanic per level, then builds the whole level around it. What if they introduced five new mechanics at once? Would any of them be memorable? What's the ONE thing that makes Mario memorable? (Jumping!) What's the ONE thing that makes Portal memorable? (The portal gun!) What will be the ONE thing people remember about YOUR game?

Every game needs one memorable thing. Not ten memorable things — one. The signature feature is what players remember and talk about. It should emerge from the systems you've already built, not be added on top.
Ami — Boss Encounter

One unique boss encounter at Tier 3. Triggers only when riskLevel exceeds a high threshold. The boss has higher power, a unique console message, and a bigger XP reward. Not cinematic. Not animated. Just distinct logic.
Ida — Car Unlock

When karma >= 400, unlock "Car Mode." Car Mode increases movement speed and grants access to the second block (a new area). No vehicle model needed — just speed increase and area access.

Time: 15 minutes | Materials: Timer, paper for scoring

Each kid has 30 seconds to describe their signature feature to the other person. No rambling. No "and also." Just: what is it, when does it trigger, and why is it exciting.

The listener rates the pitch 1–5 on three criteria:

  1. Is it exciting? (Does it make you want to play?)
  2. Is it clear? (Can you explain it back in one sentence?)
  3. Does it fit the game? (Does it grow from existing systems, or feel bolted on?)

Then switch roles. Repeat until both pitches score 4 or higher on all three criteria.

Example pitches:

  • Ami: "When your risk level maxes out, a Boss appears — way stronger than anything else. Beat it, and you get triple XP. Lose, and you lose everything."
  • Ida: "When you hit 400 karma, you unlock a car. You move faster and can reach a whole new block of lots to build on."
  • Define the signature feature unlock condition
  • Write the trigger check (when does it fire?)
  • Implement the special behavior
  • Add a distinct console message or visual cue
  • Test: feature triggers only when condition is met
  • Test: feature feels distinct from normal gameplay
  • Document the feature in your VERSION_1 plan
    •
    Checkpoint

    Signature feature triggers correctly and feels special. It's distinct from regular gameplay.

    No second boss. No second vehicle. No customization. One signature feature, fully implemented.

    Making the signature feature too complex — it should be one clear behavior, not a system of its own.

    Triggering it too easily (not special) — if the boss appears every other encounter, it's not a boss. If Car Mode unlocks in 5 minutes, it's not earned.

    Breaking the core loop to accommodate it — the signature feature enhances the loop, it doesn't replace it.

    Adding a second "just one more" feature — one means one.

    This is the hardest discipline day. They will want to add more. Hold the line. Ask: "If you had to describe your game in one sentence, what's the one thing that makes it unique?" That's the signature feature. Everything else is Version 2.

    During the elevator pitch: Be a tough audience. If the pitch takes more than 30 seconds, it's too complex. If you can't explain it back in one sentence, it's not clear enough. The constraint forces clarity.

    If they want two signature features: Ask them to pick one. Then ask them to pitch just that one. If they can't let go of the second one, ask: "Which one is more exciting?" The answer is always obvious. The hard part is accepting it.

    Watch for scope creep disguised as "polish": "I just want to add a special animation" is a new feature, not polish. Today's rule: one behavior, fully working. Visual flair is Week 5.

    Looking ahead: Tomorrow we expand the world — your game grows based on what you've unlocked.