4.1 KiB
Reflection Template For Mono-Black Reanimator
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: identify whether the game was won or lost by speed, protection, graveyard access, battlefield pressure, card volume, or storm closing. Record the decisive turn and whether the final committed line used Entomb plus Reanimate, Sorin, Imperious Bloodlord plus Saint Elenda, Necrodominance, Necropotence, Beseech the Mirror, or Tendrils of Agony.
-
Mulligans: record whether each opener had a functional black source, an acceleration piece, a payoff, and either protection or selection. Flag hands kept on Dark Ritual or Chrome Mox that lacked a clear payoff, and hands kept on Vampiric Tutor or Demonic Tutor that were too slow against the revealed opponent plan.
-
Mana: record every game where Vault of Whispers, Blooming Marsh, Darkbore Pathway, Swamp, Boggart Trawler, Fell the Profane, Chrome Mox, or Dark Ritual failed to produce the needed legal action on time. Separate true mana shortage from sequencing mistakes such as imprinting the wrong card under Chrome Mox or spending Dark Ritual before the protected payoff window.
-
Velocity: record whether Vampiric Tutor, Demonic Tutor, Entomb, and Beseech the Mirror found the correct axis quickly enough. Mark any game where repeated search effects improved hand quality but failed to convert into Reanimate, Sorin, Imperious Bloodlord, Necrodominance, Necropotence, or Tendrils of Agony before the opponent stabilized.
-
Engines: record whether Necrodominance and Necropotence were decisive reloads, win-more plays, or life-total liabilities. Track how many cards were converted into meaningful legal actions before the opponent's next pressure point, and note any game where extra cards stranded because mana, timing, or hand-size restrictions mattered.
-
Reanimation: record each Entomb and Reanimate target decision and whether Atraxa, Grand Unifier or another legal graveyard target was correct for the visible board. Flag high-life Reanimate lines that lost to combat, burn, or known interaction despite producing cards.
-
Midrange pivot: record whether Sorin, Imperious Bloodlord and Saint Elenda stabilized games where the graveyard plan was contested. Card text check required for exact Saint Elenda and Sorin, Imperious Bloodlord outcomes if the log does not expose combat, counters, tokens, or life-change details.
-
Interaction: record whether Grief, Duress, March of Wretched Sorrow, Culling Ritual, Vexing Bauble, Faerie Macabre, and Leyline of Sanctity answered the actual losing axis. Note whether discard took the card that stopped the next decisive line or merely the strongest-looking revealed card.
-
Sideboard: record whether added role cards matched the opponent's revealed plan. Flag games where Leyline of Sanctity, Culling Ritual, March of Wretched Sorrow, Vexing Bauble, Faerie Macabre, Duress, or the second Tendrils of Agony diluted the main engine without changing the matchup's decisive interaction.
-
Closing: record every game where Tendrils of Agony was available but not lethal, and every game where Beseech the Mirror, Dark Ritual, Chrome Mox, and cheap spells created enough storm pressure. Separate failed storm math from correct non-storm pivots into Atraxa, Grand Unifier or Saint Elenda.
-
Mistakes: flag missed legal actions, premature tutors, exposed Entomb lines, unnecessary life payments, wrong Chrome Mox imprint choices, pass decisions into visible pressure, and any line where the agent ignored public information from Grief, Duress, Faerie Macabre, or visible graveyards.
Existing User Requests
No additional user reflection requests were supplied.