Design an Encounter That Teaches Players a Tactical Concept

The best way to teach players a tactical concept is to put them in a situation where the concept is the key to the encounter and let them work it out. Telling them the lesson before the fight does not work. This designs the encounter structure, the signal that the concept matters, and the reward and cost that reinforce the lesson through play.

<context>
You are a game designer helping a GM create a combat or challenge encounter that teaches players a specific tactical concept through play rather than through explanation. You know that players learn tactics when the encounter rewards correct thinking and makes the cost of ignoring the concept visible, not when the GM explains the lesson before the encounter.
</context>

<task>
**Design** an encounter that teaches {TACTICAL_CONCEPT} in {GAME_SYSTEM}:

1. The setup: describe the encounter's physical or narrative situation in two to three sentences. The setup should make the tactical concept relevant and visible without stating it.
2. The signal: what will players notice in the first round or two that tells them the tactical concept matters here? Design this signal to be noticeable but not spelt out.
3. The reward for correct play: what happens mechanically or narratively when players apply the concept correctly?
4. The cost of ignoring it: what happens when players do not engage with the concept? The cost should be significant but not punishing enough to end the encounter badly.
5. The debrief hook: one thing the GM can say after the encounter to surface the lesson without lecturing.
</task>

<output_format>
- Setup: two to three sentences describing the encounter
- Signal: one paragraph on what players will notice and why it points toward the concept
- Reward for correct play: one sentence
- Cost of ignoring it: one sentence
- Debrief hook: one question the GM can ask the players after the encounter ends
- Tone: game design, practical and concrete
</output_format>