4.0 KiB

Reflection Template For Boros Dragons

For each loss, name one primary cause and one secondary cause. For each win, name the card, package, or tactical policy that most contributed to the win. Classify each result as a card quantity problem, card selection problem, mana problem, tempo problem, matchup problem, sideboard problem, pilot sequencing problem, or closing-power problem. Report mana performance, sideboard impact, stranded cards, overperforming cards, underperforming cards, and whether the Deck Strategy or Tactical Policy guidance was followed.

  • Deciding factor: Record whether the game was decided by early pressure, Dragon combat, mana stumble, removal timing, sideboard hate, or failure to close after stabilizing. Name the exact cards that mattered, especially Magmatic Hellkite, Nova Hellkite, Dragonhawk, Fate's Tempest, Twinflame Tyrant, Sarkhan, Dragon Ascendant, Momo, Friendly Flier, Clarion Conqueror, Voice of Victory, Burst Lightning, and Get Lost.

  • Mulligans: Check whether the kept hand had a castable early play, both colors when needed, and a credible path to a Dragon or repeated pressure. Flag keeps where Cavern of Souls, Mountain, Dalkovan Encampment, Sundown Pass, Multiversal Passage, Inspiring Vantage, Sacred Foundry, or Sunbillow Verge failed to support the visible sequence.

  • Mana: Track every turn where a spell was stranded by color, land timing, or Cavern of Souls not casting noncreature spells. Note whether Burst Lightning, Get Lost, Boros Charm, Daydream, Practiced Offense, or Spectacular Tactics sat unused while a creature-only land could cast threats.

  • Velocity: Record whether Boros Dragons spent turns affecting the board before the first large flyer. If the deck lost before Magmatic Hellkite, Nova Hellkite, Dragonhawk, Fate's Tempest, Purging Stormbrood, or Twinflame Tyrant became relevant, mark whether the failure was mana, no early creature, too many reactive cards, or an incorrect keep.

  • Engines and synergy: Check whether Sarkhan, Dragon Ascendant, Maelstrom of the Spirit Dragon, Momo, Friendly Flier, Clarion Conqueror, The Legend of Roku, and Lorehold, the Historian contributed to pressure, mana, card flow, or combat. Card text check required for uncertain engine roles; judge only from legal actions and resolved public outcomes.

  • Removal: Review whether Burst Lightning and Get Lost answered the highest-impact visible threat or were spent on replaceable creatures. Record missed chances to remove planeswalkers, combo permanents, large attackers, blockers preventing lethal, or targets that changed the race.

  • Sideboard: Verify whether each added sideboard card had a visible job in the matchup. Track Requisition Raid, High Noon, sideboard Get Lost, Slagstorm, Exorcise, Authority of the Consuls, Rest in Peace, Doorkeeper Thrull, Erode, and Day of Judgment by whether they were drawn, cast, stranded, or irrelevant.

  • Closing: Record turns where lethal or a two-turn clock was available but the pilot passed, overprotected a threat, or used interaction defensively without needing to. Check whether Boros Charm, Spectacular Tactics, Burst Lightning, or a Dragon attack could have ended the game under legal action text.

  • Role: Ask whether the pilot correctly identified beatdown, stabilizer, or attrition role after the first three turns. Flag games where the deck played too defensively with a strong curve or too aggressively while behind on board.

  • Mistakes: List any legal-action choice that looked inconsistent with visible board state, known public information, or matchup role. Separate likely pilot mistakes from rules-engine limitations, card-text uncertainty, and hidden-information guesses.

  • Stranded cards and performers: Name cards stuck in hand for multiple turns and why. Name overperformers and underperformers separately for main deck and sideboard, with special attention to Daydream, Practiced Offense, Spectacular Tactics, Boros Charm, Twinflame Tyrant, Purging Stormbrood, and sideboard hate cards.

Existing User Requests

No additional user reflection requests were supplied.